馃悰 Handle bootstrap npm dist-tags - #25
Merged
Merged
Conversation
Record npm assigning latest during the package's first registration and allow only the known bootstrap verification to accept it. Future prerelease verification still rejects moving latest to the prerelease version.
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
1.0.0-rc.0bootstrap and trusted-publisher setuplatestonly for the known first-registration bootstraplatestThe package publication and provenance succeeded in release run #30971442298. Its announcement job stopped because npm assigned both
nextandlateston the first package registration; the maintainer accepted that temporary state until stable1.0.0replaceslatest.Checks
npm run format:checknpm run lintnpm run typechecknpm test(76 tests)1.0.0-rc.0with the scoped bootstrap exceptiongit diff --check