chore: fix config to support next prerelease
#1697
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
jzempel
commented
Feb 5, 2024
| steps: | ||
| - *attach_workspace | ||
| - run: npm set //registry.npmjs.org/:_authToken=$NPM_TOKEN | ||
| - run: npm exec -- lerna publish from-git --ignore-scripts --no-verify-access --yes |
There was a problem hiding this comment.
removes a deprecated Lerna flag – all access is now verified by default
geotrev
approved these changes
Feb 5, 2024
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.
Description
The config updates and fixes in the PR allow the positional tag
versionspecifier to work as intended. For example:npm run tag preminorwould ensure that the version is set with-next.xnotation and that it is published under thenexttag.