chore: Verify that the tag used for publishing matches the version number #1067
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
mhawryluk
reviewed
Mar 25, 2025
|
|
||
| if (!tagVerified) { | ||
| throw new Error( | ||
| `Publishing under a mismatched tag "${chosenPublishTag}" for version ${packageJSON.version}.`, |
There was a problem hiding this comment.
If I'm not mistaken if there's no tag provided (it's undefined) then this will always throw. and e.g. for typegpu package (currently not alpha) we want there to be no tag. so I think the logic for undefined needs to be changed, we cannot look for "undefined" in version number
|
pkg.pr.new packages benchmark commit |
mhawryluk
approved these changes
Mar 31, 2025
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.
No description provided.