Repository navigation
fix(publish): approve the v21.7.2 publisher for organization settings - #6408
Conversation
Trust the .github manifests publisher at d70d506 (v21.7.2) alongside f336227, which signs the settings applied today, and retire 2666bae. Refs #6407 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The only rendered authorization change is the github-config OCIRepository signer subject rotated in the previous commit. Refs #6407 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai review |
Action performed
|
✅
|
✅
|
|
No actionable comments were generated in the recent review. Walkthrough
Severity of issue fixed: Medium Merge Risk:
|
Readiness at
|
The only change to the reviewed publisher files since f336227 is the harden-runner v2.22.3 -> v2.22.4 pin (#918); both helper blobs are unchanged. The platform consumer approves d70d506 in devantler-tech/platform#6408. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…fests.yaml from 21.3.1 to 21.7.2 (#951) * fix(deps): bump devantler-tech/.github/.github/workflows/publish-manifests.yaml Bumps [devantler-tech/.github/.github/workflows/publish-manifests.yaml](https://github.com/devantler-tech/.github) from 21.3.1 to 21.7.2. - [Release notes](https://github.com/devantler-tech/.github/releases) - [Commits](f336227...d70d506) --- updated-dependencies: - dependency-name: devantler-tech/.github/.github/workflows/publish-manifests.yaml dependency-version: 21.7.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> * fix(deps): record the consumer-approved v21.7.2 manifests publisher The only change to the reviewed publisher files since f336227 is the harden-runner v2.22.3 -> v2.22.4 pin (#918); both helper blobs are unchanged. The platform consumer approves d70d506 in devantler-tech/platform#6408. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nikolai Emil Damm <nikolaiemildamm@icloud.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Why
The organization-settings repository cannot take its latest publisher update until this platform trusts that publisher to sign its settings. Without that trust, the next settings release would be refused by the cluster and organization changes would stop applying.
What
The platform now trusts the publisher that signed the settings running today and the new publisher, and stops trusting the one before them. The running settings keep verifying, and the next release can be signed by the new publisher.
Fixes #6407