chore(deps): bump actions/checkout from 4 to 6 - #3
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 |
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/checkout-6
branch
2 times, most recently
from
April 25, 2026 00:13
ba0402a to
2298b1b
Compare
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/checkout-6
branch
from
April 30, 2026 20:49
2298b1b to
91093e4
Compare
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>
phoenixtekk
added a commit
to phoenixtekk/openpartner
that referenced
this pull request
Aug 31, 2026
Upstream hardcodes 'OpenPartner' across the portal — brand fallback, logo alt text, the review banner, settings hints, and the bank-debit authorisation. A self-hosted operator selling this as their own product needs all of it to carry their name, as one edit rather than twenty. New lib/platform.ts holds PLATFORM_NAME; DEFAULT_BRAND now derives from it, so every unbranded surface follows automatically. The consequential one is admin/Billing.tsx. Its checkbox read 'I authorize OpenPartner to debit our bank account', linking to openpartner.dev/terms. Both are wrong for this deployment and would have been wrong in a way that matters: it names the incorrect legal entity as the party taking money out of a customer's bank account, under a third party's terms document that does not govern the relationship. Now PLATFORM_LEGAL_ENTITY and a Phoenixtekk terms URL, with the constant carrying a warning that the document must exist and be reviewed by counsel before HOSTED_FUNDING_ENABLED is ever set. Network- and creator-scoped copy still says OpenPartner; those surfaces are hidden by patch getcoherence#3, so they are cosmetic and deliberately left for a merge with upstream rather than churned now. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
phoenixtekk
added a commit
to phoenixtekk/openpartner
that referenced
this pull request
Aug 31, 2026
Another Network surface that escaped patch getcoherence#3. 'Sign up as a creator' points at /creator/signup, which is only meaningful with a Network coordinator — we run none, so it led nowhere. Spotted on the live sign-in page. 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 actions/checkout from 4 to 6.
Release notes
Sourced from actions/checkout's releases.
... (truncated)
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
de0fac2Fix tag handling: preserve annotations and explicit fetch-tags (#2356)064fe7fAdd orchestration_id to git user-agent when ACTIONS_ORCHESTRATION_ID is set (...8e8c483Clarify v6 README (#2328)033fa0dAdd worktree support for persist-credentials includeIf (#2327)c2d88d3Update all references from v5 and v4 to v6 (#2314)1af3b93update readme/changelog for v6 (#2311)71cf226v6-beta (#2298)069c695Persist creds to a separate file (#2286)ff7abcdUpdate README to include Node.js 24 support details and requirements (#2248)08c6903Prepare v5.0.0 release (#2238)