Repository navigation
Approve the v20.1.17 publisher for organization settings #6003
Description
🤖 Generated by the Agentic Engineer
Problem
The organization settings repository has a pending dependency update (devantler-tech/.github#889) that moves its settings publisher from v20.1.12 to v20.1.17. The platform only accepts organization settings releases signed by publisher versions it has approved, so that update is refused by its own guard until the platform approves the new publisher version.
Evidence
- fix(deps): bump devantler-tech/.github/.github/workflows/publish-manifests.yaml from 20.1.12 to 20.1.17 .github#889 fails
test-publish-contractswith "signer revision is not approved by consumers". - Between the two publisher versions the publishing workflow and its two helper scripts are unchanged; only the signer identity moves.
- The live organization settings source reads Ready today, signed by the v20.1.12 publisher.
Acceptance criteria
- The platform accepts the v20.1.17 publisher next to the v20.1.12 one, and stops accepting the older v20.1.6 one.
- The approval self-test covers the new accept and the retired reject.
- After merge, the live organization settings source still reads Ready.
Size: small.
Reacted by coderabbitai
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
None yet
Projects
- Status
Activity
coderabbitai commentedon Nov 10, 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!
chore: agent-claim #6003 nonce=5eaf40251566a39cc15c32c87fc160b2