Skip to content

Restore verified organization settings publication after the publisher transition #5265

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

The organization settings publication is blocked after its caller moved to a new shared publisher in devantler-tech/.github#725. The platform's explicit publisher approvals still accept the previous transition pair, so signature verification correctly refuses the new publication. The last verified artifact remains available.

Expected outcome

Restore verified publication delivery through a narrowly reviewed publisher transition. Retain the currently applied publisher, retire the obsolete approval covered by #5240, and approve the exact new revision only after reviewing its source. Keep the existing issuer, repository and consumer boundaries.

Acceptance criteria

  • Bind the current applied publication and the new publication to their exact shared workflow revisions and review the new workflow source.
  • Update the canonical approval, generated acceptance rule and authorization evidence through their existing procedures, retaining the current verified publisher.
  • Prove the retained and new revisions are accepted while the retired revision and unrelated issuers, repositories and revisions are rejected.
  • Obtain an independent review at the tested head and deliver through the protected path.
  • Read back the deployed rule, verified new publication and healthy platform status.

This live delivery failure preempts production activation of the security dashboards in #5260. The dashboards themselves were implemented in #5262.

Activity

  1. self-assigned this
    on Oct 23, 2026
  2. added theissue type on Oct 23, 2026
  3. moved this to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Oct 23, 2026
  4. removed their assignment
    on Oct 23, 2026
  5. self-assigned this
    on Oct 23, 2026
  6. added a commit that references this issue on Oct 23, 2026
  7. moved this from 🏃🏻‍♂️ In Progress to 👀 In Review in 🌊 Project Boardon Oct 23, 2026
  8. moved this from 👀 In Review to 🚀 Ready to Merge in 🌊 Project Boardon Oct 23, 2026
  9. moved this from 🚀 Ready to Merge to ✅ Done in 🌊 Project Boardon Oct 23, 2026
  10. devantler commented on Oct 23, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Delivered through #5266 at reviewed head 1634dddd44b423fc52ba82080b114f0efaa8e12f; the protected merge-group run 39961170965 passed and merged as 9003ce4c8b1c17916d5db085a2c3bd3312296824 at 14:29:23 UTC.

    Read-only production verification at 14:29 UTC:

    • The deployed rule contains exactly the reviewed retained/new canonical pair (0f390329… and 6f1dee95…), with the legacy family unchanged and retired 8d2203af… absent.
    • The current publication is v12.0.4, digest sha256:4d386cdbcad81774308ff517da208f4bea9afc0d57d817cbc660ecbf83793b3c. Ready and SourceVerified are both True at the current observed generation, 33.
    • Independent Cosign verification of that exact current digest passed with the reviewed identity bounds. Its publication claims bind it to retained publisher 0f390329b590404c02565b27a263ee841fa02bce. The earlier exact v12.0.3 proof binds the new publisher, and the retained/new positive and retired/unrelated negative controls passed.
    • The full live platform health helper exited 0 with PLATFORM-HEALTH=OK.

    All five acceptance criteria are met. #5267 remains the separately tracked complete-observation refresh work; this receipt does not claim that broader task is resolved. The publication blocker on dashboard activation #5260 is cleared.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

Priority

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions