Repository navigation
docs: reconcile member gate boards with published releases - #15
Merged
Merged
Conversation
sshlg
marked this pull request as ready for review
October 13, 2026 04:47
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 owner board still described patch publication as pending after the release and npm byte readback completed. Close GATE-01/GATE-02 with the exact tagged source, successful release run and per-file published receipt; keep family installation and native acceptance separate.
Validation: structural validator and diff check passed; npm pack path set and every packaged SHA-256 remain identical to the published version. Documentation only, no package/version/runtime/workflow changes.
Draft until independent review; promote the frozen candidate once for eligible validation.