Skip to content
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

Simplify RELEASE.md with npm version #298

Merged
merged 1 commit into from
Mar 5, 2021

Conversation

minrk
Copy link
Member

@minrk minrk commented Mar 5, 2021

Using npm version is a little simpler and more natural for a javascript project than bump2version.

closes #276

package.json Outdated Show resolved Hide resolved
Using npm version is a little simpler and more natural for a javascript project than bump2version.
Copy link
Member

@consideRatio consideRatio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great to me!

bump2version --tag release
# specify the new version here,
# which should already have been chosen when updating the changelog.
npm version 1.2.3
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This in particular, explicitly stating the new version, means we can't publish the wrong thing, whereas bump2version --tag release assumes the prior state was correct for the next released version.

Copy link
Member

@consideRatio consideRatio Mar 5, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've come to appreciate that ;) (EDIT: explicitly stating version, less complexity)


```bash
bump2version --no-tag patch
npm version --no-git-tag-version prerelease --preid=dev
git commit -am "back to dev"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It still boggles my mind that npm version doesn't have a 'commit but don't tag' option

@@ -0,0 +1 @@
tag-version-prefix=
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

npm version's default is to use the v prefix on tags, but since we haven't been doing that (I don't happen like it, personally), this config lets us stay consistent.

@consideRatio consideRatio merged commit 46ce0cb into jupyterhub:main Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update release instructions
2 participants