Repository navigation
fix(release): bridge gate derives from the publication protocol, not variable presence - #181
Merged
Merged
Conversation
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.
Closes #177 (upon merge). The V3 bridge gate used to run only when
V3_BRIDGE_RELEASEwas set, treating a forgotten variable as proof of a V2 publication.scripts/check_release_gate.pynow derives the protocol from the built artifacts (ainative-release-v3.jsonorainative-lifecycle-v3-*.zipindist/): a protocol 3 publication requires a bridge a V2 runtime can actually resolve (reusingscripts/check_bridge_release.py+ the production V2 provider — no second resolver); protocol 2 reports the gate explicitly not applicable. The workflow runs it right after the dist version checks. Non-vacuity tests pin all five outcomes, including the workflow-entry-point mutation (V3 dist + unset variable -> exit 1,BLOCK RELEASE). RELEASING.md updated to the same wording. Local proof: 24 release-gate tests + docs parity green, complexity 0 findings, LOC 0 warnings.