fix: verify canonical local release artifacts - #8
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
The public release verification commands passed a relative output path into an intentionally strict canonical-directory verifier, so exact-candidate packaging could succeed while the required public verification command failed before publication.
This change makes the no-argument candidate and published commands resolve the existing source-owned macOS release directory internally. Explicit verifier APIs remain strict about absolute normalized caller paths, and malformed or trailing CLI arguments fail closed.
Validated with focused release tests, desktop typecheck and lint, policy/public-tree gates, release contract/source/remote gates, and independent review. The full desktop suite reached 2,425 passes; seven known load-sensitive git-runner cases passed 18/18 in their isolated rerun.