Bind Beta18.2 release manifest to main#257
Merged
Merged
Conversation
carlosjperez
previously approved these changes
Jul 7, 2026
carlosjperez
left a comment
carlosjperez
left a comment
Contributor
There was a problem hiding this comment.
Approved manifest source binding fix after squash merge. Scope is limited to making Beta18.2 release evidence point at the actual main commit.
carlosjperez
approved these changes
Jul 7, 2026
carlosjperez
left a comment
carlosjperez
left a comment
Contributor
There was a problem hiding this comment.
Re-approved squash-safe source binding. This keeps the manifest source commit as the main base commit so PR checks and post-squash main checks can both validate.
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
2 participants
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.
Summary\n- Updates release/manifest.json source binding after squash merge so the public Beta18.2 manifest points to the actual main commit containing the release.\n\n## Verification\n- node scripts/release-manifest-validate.js --allow-dirty\n\n## Reason\nThe previous branch manifest used a pre-squash source commit. After merge, branch commits are not ancestors of main, so the release workflow correctly failed fail-closed before publication.