-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Add new command for pre-releasing npm packages #23357
Conversation
Size Change: 0 B Total Size: 1.13 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this proposal makes sense. I had some minor concerns that are fixable. What do you think?
We can give it a try today and update publishing docs afterwards.
bin/plugin/commands/packages.js
Outdated
versionBump !== null | ||
? semver.inc( version, versionBump ) | ||
: null; | ||
|
||
if ( nextVersion !== null && isRC ) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can’t use the actual release number because Lerna uses npm version command internally that always has to bump version but we could use -pre.1
suffix that we could simply update to the final version when the actual publishing happens. I didn’t think about it earlier. Great idea, thanks ❤️
So, we would need two versions, one for the changelog and one for package.json
.
241ab13
to
ea26c91
Compare
ac618af
to
6785d3f
Compare
Explore adding a new command
npm-rc
to release npm packages to thenext
tag as pre-release.TODO: