Repository navigation
Preserve the published marketplace during npm release preparation - #2
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
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.
Keep the public devtools marketplace on the available npm 0.2.1 release. The attempted 0.2.2 publish was rejected by npm, so advertising it would make new marketplace installations fail.
Release metadata validation now allows the public catalog to remain on an older version while requiring the package, built manifest and tag to agree. The release guide makes registry verification a prerequisite for advancing marketplace and consumer pins. This changes release ordering only; Codex implementation and plugin identity are unchanged.
Validation: release metadata check, public npm 0.2.1 availability, and the existing 87-test/release-check suite.