P9-12 alpha6 mainline closure#26
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.
P9-12 closure PR for the published 0.1.0-alpha.6 corrective release.\n\nScope:\n- Carry alpha4/alpha5/alpha6 corrective evidence and package-docs alignment onto main.\n- Preserve published:verify as generator and published:verify:evidence as verifier.\n- No npm publish, dist-tag mutation, or GitHub Release mutation in this PR.\n\nCurrent live state checked before PR creation:\n- npm alpha/latest point at 0.1.0-alpha.6.\n- GitHub Release v0.1.0-alpha.6 is non-draft prerelease with tarball asset.\n\nLocal and PR gates are being run separately for P9-12 acceptance.