Repository navigation
feat(business-site): move the tenant to the signed v3.11.0 release - #6398
Conversation
v3.11.0 carries the privacy notice's portal section (business-site#628) for the invite-only sign-in switch-on (#6389), and default-off add-on features (#624, #627). Prepared with scripts/bootstrap-tenant-source.sh --prepare-canonical-upgrade against the read-only production context, on top of the settled v3.10.0 binding (#6397). Same approved publisher revision; no new approval. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pinned CI render changes exactly one entry, Tenant flux-system/business-site, from 6aca6f32… to 64886c2d…. Only its source digest changes; no authorization resource is added or removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codex review |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. 🚀 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
✅
|
✅
|

Why
The maintainer chose to switch the portal's sign-in on, invite-only. business-site v3.11.0 carries the privacy notice's portal section (devantler-tech/business-site#628). This re-pin rolls out the pods, and with #6389's
portal-settingsthey start with sign-in on and the privacy section live together.Queue order: directly behind #6389. Nobody can sign in until the maintainer invites a customer.
The release also carries:
Their migrations run in the package's migration Job first, and the new web pods serve only once the ledger holds them.
What
The business-site Tenant moves from v3.10.0 to v3.11.0, signed by the same approved publisher revision, so it needs no new approval.
scripts/bootstrap-tenant-source.sh --prepare-canonical-upgradeagainst the read-only production context, on top of the settled v3.10.0 binding (chore(security): regenerate the approved publish-workflow revisions #6397).Authorization ledger approval. The pinned kubectl v1.36.2 / Kustomize v5.8.1 render in CI changes exactly one entry, Tenant flux-system/business-site, from
6aca6f326acea4f267e0e35f8a48ce091ca7610c9bf633f13e99280431d571d3to64886c2d24943dddd25cdc30dbf2524e4ce8df7a366f5807cd274b22ecdd314e. Only its source digest changes; no authorization resource is added or removed.After merge
The agent checks:
portal schema migration completed;Part of devantler-tech/business-site#302 and devantler-tech/monorepo#3939.
🤖 Generated with Claude Code