chore(deps): bump pnpm/action-setup from 4 to 6 - #1
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Bumps [pnpm/action-setup](https://github.com/pnpm/action-setup) from 4 to 6. - [Release notes](https://github.com/pnpm/action-setup/releases) - [Commits](pnpm/action-setup@v4...v6) --- updated-dependencies: - dependency-name: pnpm/action-setup dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/github_actions/pnpm/action-setup-6
branch
from
April 30, 2026 20:49
eca1cf1 to
7455fbf
Compare
keithfawcett
added a commit
that referenced
this pull request
May 9, 2026
…e event" Adds a third trigger to the compound rule schema. Pairs with `first` to express a common dual-rate offer without the rules double-firing on event #1: - first — fires only on the FIRST event of eventType - subsequent — fires on every event of eventType EXCEPT the first Example: "50% on first invoice, 20% on every subsequent invoice" = [{trigger:'first', eventType:'invoice_paid', value:50}, {trigger:'subsequent', eventType:'invoice_paid', value:20, recurring:true}] Engine reuses the same prior-attribution lookup `first` already had, just inverted (`first` skips when prior exists; `subsequent` skips when no prior). Renderer outputs "20% recurring on every subsequent invoice" which matches how brands naturally describe the offer. UI adds the option to the trigger Select with sensible defaults per trigger. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
phoenixtekk
added a commit
to phoenixtekk/openpartner
that referenced
this pull request
Aug 31, 2026
Two Phoenixtekk divergences from upstream, both documented in the ops repo at docs/FORK-PATCHES.md. Patch getcoherence#1 — per-tenant selfhost mode. Upstream resolves a tenant's payout rail with planToMode(), where NULL falls through to the process-wide OPENPARTNER_MODE. The only way to get mode='selfhost' for a tenant was to put the WHOLE installation into selfhost mode, which also short-circuited four scheduler jobs — including usage-report, the only path by which attributed GMV reaches Stripe meters. On a hosted deployment that silently means customers are never billed for metered usage. Phoenixtekk needs both rails on one hub: own products pay affiliates by direct transfer (our own money on both sides), customer brands go through the funded rail (fronting a third party's principal is unacceptable credit exposure). - BillingPlan gains 'selfhost'; migration widens the CHECK constraint. - planToMode() returns 'selfhost' for it, so the rail is decided by the tenant's own row. - The four global getMode()==='selfhost' scheduler gates are removed. Verified safe: every function they guarded already resolves billing state per tenant and no-ops for selfhost — reportUsageToStripe() returns "not configured for mode=selfhost", subscription reconcile only touches tenants holding a Stripe subscription id, and hasActivePlan() reports selfhost as entitled so the white-label sweep never revokes it. - POST /import moves from the global gate to a per-tenant one; previously, running the install in selfhost mode opened partner import for EVERY tenant, customers included. 'selfhost' is not accepted by POST /signup or the billing route — both hardcode z.enum(['flex','revshare']) — so a brand cannot self-declare onto the unfunded rail. Operator assignment only. Patch getcoherence#3 — gate Network surfaces on NETWORK_URL. The Network is OpenPartner's own federated creator-discovery service. We do not run one, so its UI rendered a 503 (network_not_configured) on the ops console's Creators tab and shipped dead nav to brands and partners. The API now reports networkEnabled on /config/program and /platform-admin/me, and the portal hides every Network route and nav entry when it is false. Routes are gated too, not just links, so direct navigation cannot reach a page that can only error. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps pnpm/action-setup from 4 to 6.
Release notes
Sourced from pnpm/action-setup's releases.
Commits
26f6d4ffix: use npm co-located with the action node binary (#239)903f9c1fix: update pnpm to 11.0.0-rc.5bdf0af2test: add strict version-match jobs to reproduce #225 / #22771c9247fix: pnpm self-update binary shadowed by bootstrap on PATH (#230)078e9d4fix: update pnpm to 11.0.0-rc.208c4be7docs(README): update action-setup version5798914chore: update .gitignoreddffd66fix: remove accidentally committed fileb43f991fix: update pnpm to 11.0.0-rc.03852509README.md: bring versions up-to-date (#222)