fix(ci): load release gate from event-bound main - #75
Merged
Conversation
This was referenced Sep 1, 2026
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.
Why
An existing release PR can retain an older
pull_request.base.sha. The first live readiness run therefore checked out a base commit that predated the gate script and failed withMODULE_NOT_FOUNDinstead of evaluating publication controls.Fix
pull_request_targetand pinned checkout v7 use the event-bound trusted default-branch ref and SHArefandpersist-credentials: falseVerification
After merge, PR #66 will be refreshed and must fail for the expected publication-readiness switches, not for a missing module.