-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(publish): validate dist-tag #7459
Merged
Merged
Conversation
This file contains 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
Will definitely want a test for this one. |
wraithgar
changed the title
fix: validates tag on publish
fix: validate dist-tag on publish
May 1, 2024
wraithgar
changed the title
fix: validate dist-tag on publish
fix(publish): validate dist-tag
May 1, 2024
Flakey Linux 20.x test?
|
Yep, known issue in testing only. It's on the backlog. |
wraithgar
reviewed
May 1, 2024
wraithgar
approved these changes
May 1, 2024
Merged
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.
Currently as described in #7275 the publish command lacks the same check that
npm install
andnpm dist-tag add
have to validate that the tag is valid (url encoded correctly via npa.js here). There's many ways to do this, or places this can go, totally open to putting this in a more appropriate place if there is one.I tested this locally:
Shown error locally