fix(release): publish only tested revisions - #295
Merged
Merged
Conversation
pathscale
force-pushed
the
fix/release-gate-pinning
branch
from
September 13, 2026 05:24
26c41f9 to
a29b6dc
Compare
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
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.
The release workflow could publish a revision that had not passed CI, while the rendered QA host and driver also floated between runs. A successful CI run on
masternow releases only its exact tested SHA, stops ifmasteradvances, tags the exact packaged revision, and uses reviewed Bun, Chuzz, and ps-qa versions.The repository contract now records the no-lockfile policy and the exact ps-qa release requirement.
Validation:
ps-qa 0.7.3and pinned Chuzz: 101/101onChangeEndNo component behavior or package version changes in this PR. Publication remains automatic after merge and successful CI; this PR does not publish or deploy anything.