Repository navigation
Approve the publish-app v20.1.1 publisher for business-site #5860
Description
🤖 Generated by the Agentic Engineer
Evidence
business-site#496 moves the site's runtime publisher to devantler-tech/.github/.github/workflows/publish-app.yaml@16f1a6c96aaf2581885e17389a0e0f9f42387970 (v20.1.1). The platform admits a tenant's runtime only from a publisher listed for it in scripts/publish-workflow-canonical-approvals.tsv. Today that list approves 467f0758 and af042c54 for business-site, and #5830 (in the merge queue) adds the identity of the currently published v3 runtime. 16f1a6c9 is not listed.
Problem
Once business-site#496 merges, the next enabled runtime release would be signed by a publisher the platform does not accept, so staging and production would keep the older runtime.
Proposed change
Add business-site publish-app devantler-tech/.github 16f1a6c96aaf2581885e17389a0e0f9f42387970 to the approvals list, together with the approved-surface and test fixtures that move with it, following the shape of #5821. The only change to publish-app.yaml in the d8b5d0e9 → 16f1a6c9 range is a patch bump of the hardened-runner action.
Acceptance criteria
- The approvals list and its tests accept
16f1a6c9for business-site and still reject an unlisted commit. - Once fix(staging): admit the verified business-site v3 runtime #5830 has merged, this does not remove the identities it admits.
Size
Small. One approvals row and its fixtures.
Activity
coderabbitai commentedon Nov 3, 2026
🔗 Related PRs
#5748 - feat: support business publisher transitions [closed]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!