Require version bumps and published releases for extension merges - #200
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.
Extension changes can reach main with only a local ZIP and no published release. Require each extension-changing PR to bump the manifest above current main, then publish a versioned GitHub release from the exact merged revision after complete CI succeeds.
The canonical checklist covers the root manifest, ZIP/checksum/download metadata, published asset readback, concurrent version checks and extension-only tags. GitHub publication, deployment and Chrome Web Store publication remain separate receipts; documentation-only changes need no extension bump.
Validation: formatting, harness/generated documentation checks, public documentation build and release/source link checks. No runtime or permission changes.