Repository navigation
feat(business-site): move the tenant to the v21.3.4-signed v3.2.3 release - #6243
Conversation
…ease Business-site v3.2.3 is signed by publish-app v21.3.4 (a76d5df9), whose bundle nodes can find (#6226). Approve a76d5df9 for business-site in place of the unused v19.0.12 slot, keeping the current af042c54 pin, and copy the generated canonical upgrade (published-upgrade binding and Tenant digest and publisher). Update the Tenant ledger line and static-scan instance hash from their validators. The staging hold is unchanged. Fixes #6229 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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: 3fc89d3
- CodeRabbit: rate limited on this repository at 2026-11-14T01:22Z ("Review limit reached", next included review ~02:17Z)
- Codex: usage limit since 2026-11-13T21:39Z (review-lane-health DOWN, maintainer-only)
- Cursor Bugbot: usage limit since 2026-11-13T15:46Z (review-lane-health DOWN, maintainer-only)
Verdict: no P0/P1 findings
✅
|
✅
|
Readiness at 3fc89d3
|

Why
The business-site app cannot start because nodes cannot find a usable signature on its current image (#6226). Business-site has now cut a new release signed by the newer publisher version the platform already trusts.
What
The platform moves business-site to that verified release and approves that publisher version for business-site in place of an older one nothing uses. The staging hold stays in place; lifting it stays with #6214 once the pods are Ready.
Fixes #6229
👉 After merge/promotion: the agent checks that the business-site pods become Ready, then unparks #6214.