fix: use workflow identity instead of dynamic run title - #327
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Use the existing strict workflow path, repository, branch, and exact source revision checks for Runtime identity. Do not treat GitHub's dynamic display title as the workflow name.
The real source uses a dynamic run-name. The previous fixed-title check stopped before any broker reads. No title whitelist is added; all source, attempt, latest-run, broker scope, report, and publishing guards remain.
Verification
60 account-facts tests passed, including dynamic-title cases and rejection for the same title with the wrong path, repository, or SHA. Ruff, compile, and diff checks passed. Actual protected source binding adoption and balance acceptance remain separate.