Repository navigation
chore(security): regenerate the approved publish-workflow revisions - #6197
Conversation
This regeneration was dispatched after devantler-tech/business-site#560 and devantler-tech/aws#81 restored both tenants to platform-approved publishers. It is the first run to pass since 2026-11-03 (#5267). Driving it to merge. @coderabbitai review |
Action not completed
|
|
Important Review skippedThis PR was authored by a bot without an assigned CodeRabbit review seat. Ask an organization administrator to assign a seat to the bot. See the seat-assignment guide. After the seat is assigned, request a review again.
|
devantler
left a comment
There was a problem hiding this comment.
🤖 Generated by the Agentic Engineer
Self-review (fallback — CodeRabbit, Codex and Cursor Bugbot unavailable)
Reviewed commit: e9034d8
- CodeRabbit: skipped at 2026-11-13T08:58:55Z on this PR ("Review skipped": authored by a bot without an assigned CodeRabbit review seat)
- Codex: usage limit at 2026-11-13T01:07:39Z on devantler-tech/.github#916 ("You have reached your Codex usage limits for code reviews"); lane DOWN, no completed review since 2026-11-12T04:47:01Z
- Cursor Bugbot: account mismatch at 2026-11-13T03:29:37Z on bot-authored devantler-tech/ksail#8242 ("does not match the PR author"); usage limit at 2026-11-12T22:36:57Z on #6151
Verdict: no P0/P1 findings
✅
|
✅
|
… builds on its settled binding Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v3.2.1 is the first business-site release with the two-host runtime and the package-owned public and portal routes. It is signed by the approved publish-app revision d8b5d0e9, as v3.0.0 was. - The binding and the Tenant digest are the unedited output of `bootstrap-tenant-source.sh --prepare-canonical-upgrade --tag v3.2.1`, run against the settled v3.0.0 binding from #6197 and a read-only production context. The preparation verified the release (cosign, tag v3.2.1, source 16cf60a0, run 43400872692) and the live v3.0.0 source (Ready, generation 3). - The Tenant keeps #6174's enabled flags; only its digest moves to sha256:eec71bcf…c66e4. - The rendered authorization surface and the static-scan baseline move only the business-site Tenant entry. Part of #6177 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Why
The cluster only trusts releases signed by publishing-workflow revisions it
has approved. A consumer's deployed release or workflow pin has moved,
so the approved list is out of date.
What
Refresh the approved list and each consumer's matcher from what is deployed
and what each consumer currently pins. Every consumer resolved on both halves,
and each matcher accepts exactly its approved revisions.
No issue: trivial fix.