Repository navigation
Approve the v20.0.3 publisher for organization settings #5822
Description
🤖 Generated by the Agentic Engineer
Evidence
devantler-tech/.github#847moves the organization settings publisher from v19.0.8 to v20, and its contract test refuses: the new revision is not approved by the platform.- Between v19.0.8 and v20.0.3,
require-unpublished-version.shandrecover-manifests-version.shkeep their blobs.publish-manifests.yamlchanges one line: the Flux CLI action moves from v2.9.6 to v2.10.0, pinned to the upstream tag's commit. v20.0.1 and v20.0.3 publish identical content, so the approval targets the newest, v20.0.3. - The live settings source serves release 20.0.3 and reads Ready (read 2026-11-03). That release was built while
.githubpinned v19.0.8, so v19.0.8 must stay accepted.
Outcome
The platform accepts the v20.0.3 publisher for organization settings, deployed before .github switches to it, so the next settings release is not refused.
Acceptance
- The approvals table and the source's identity pattern name the v20.0.3 commit. v19.0.8 stays accepted, and v19.0.3 is retired because a consumer accepts at most two canonical commits.
- After deployment, the live source still serves the current release and reads Ready.
.github#847can then move to v20.0.3 and update its reviewed content record and recorded signer.
Reacted by coderabbitai
Activity
coderabbitai commentedon Nov 3, 2026
🔗 Related PRs
#5266 - fix(security): restore verified organization settings publication [merged]
📝 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!