Skip to content

chore(security): regenerate the approved publish-workflow revisions - #5276

Merged
devantler merged 1 commit into
mainfrom
regenerate-publish-workflow-approved-revisions
Oct 24, 2026
Merged

devantler merged 1 commit into
mainfrom
regenerate-publish-workflow-approved-revisions

Conversation

@botantler-1

@botantler-1 botantler-1 Bot commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

🤖 Generated by the Agentic Engineer

Why

The cluster only trusts releases signed by publishing-workflow revisions it
has approved. A consumer's deployed release or workflow pin has moved,
so the approved list is out of date.

What

Refresh the approved list and each consumer's matcher from what is deployed
and what each consumer currently pins. Every consumer resolved on both halves,
and each matcher accepts exactly its approved revisions.

No issue: trivial fix.

@devantler

Copy link
Copy Markdown
Contributor

🤖 Generated by the Agentic Engineer

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor
⚠️ Action not completed

Review skipped.

@coderabbitai

coderabbitai Bot commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

This PR was authored by a bot without an assigned CodeRabbit review seat. Ask an organization administrator to assign a seat to the bot. See the seat-assignment guide. After the seat is assigned, request a review again.

Run configuration
  • Source mode: Auto
  • Repository: devantler-tech/platform
  • Branch: main
  • File: .coderabbit.yaml
  • Commit: e04d14f
  • Layers: Repository YAML (base), Organization UI (inherited)
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 73401fee-fcf3-4fb4-a243-23aab71e68ab

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@devantler

Copy link
Copy Markdown
Contributor

🤖 Generated by the Agentic Engineer

CodeRabbit’s authenticated response to this request reports no review for this bot-authored PR (cause class: quota/billing). The no-gate guard independently returned ADMIT for the unchanged head. cr:no-gate@a48007af7c969edfa1dcd9c5d4da6727ec799dd1. Advancing to Codex under the ordered review procedure; readiness and review success are not claimed.

@devantler

Copy link
Copy Markdown
Contributor

🤖 Generated by the Agentic Engineer

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-24T08:46:02.121248Z a48007a Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: a48007af7c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@devantler

Copy link
Copy Markdown
Contributor

🤖 Generated by the Agentic Engineer

Evaluated the complete one-file change at a48007a as the release maintainer. It refreshes the observed publication inventory; the approved identity set, executable workflow and runtime matchers do not change. The newly recorded publisher revision was already approved for this consumer.

Observed the real generator run 40071335218: it resolved the deployed publications and default-branch pins, verified all five consumer matchers, and created this exact signed head and PR. Current-head CI 40078638228 passed the repository guards, regeneration controls and 53 ablations. Its rendered-source guard verified all nine repositories retain signature verification; the matcher job passed actual package signatures and both identity-negative controls. All 39 reported check runs are success/skipped, all readable required gates passed, and there are zero review threads or body findings. The native code-quality rule remains UNVERIFIED by the helper; GitHub reports CLEAN and remains the authority for that rule.

Codex completed a clean review at this exact head (receipt). The programmed-updater classifier does not recognize this publisher-refresh shape, so I used the complete static review and hosted-behaviour path and executed no PR branch locally. No new approval or trust exception is inferred. Ready for the protected merge queue; deployment and post-merge verification remain outstanding.

@devantler
devantler marked this pull request as ready for review October 24, 2026 10:51
@devantler
devantler self-requested a review as a code owner October 24, 2026 10:51
@devantler
devantler added this pull request to the merge queue Oct 24, 2026
Merged via the queue into main with commit 6b7cc2b Oct 24, 2026
40 checks passed
@devantler
devantler deleted the regenerate-publish-workflow-approved-revisions branch October 24, 2026 11:18
@github-project-automation github-project-automation Bot moved this from 🫴 Ready to ✅ Done in 🌊 Project Board Oct 24, 2026

Copy link
Copy Markdown
Contributor

🤖 Generated by the Agentic Engineer

Post-merge verification completed for source a48007af7c969edfa1dcd9c5d4da6727ec799dd1, merged as 6b7cc2bc2e6d05573cd5e58ce63e16dc4dc665c2. The source head is unchanged from the evaluated queue admission, and main still names this merge.

The protected merge-group CI and deployment succeeded, including the actual publication-signature matcher checks. All ten actual-main validation jobs passed. Its production-convergence job reported CONVERGED at that exact merge revision; no corrective redeployment was required. Release, TODO and the two native push-analysis workflows also completed successfully. This closes the deployment and post-merge verification left outstanding in the readiness record.

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

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

1 participant