We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The release process right now is cumbersome af. Right now, we have to:
But wait...the changelog doesn't get updated!
I say we simplify this using standard-version at all times (we already refer to it in various files as the guideline for commits). This way we can:
standard-version
standard-version -s "chore(release): %s"
git push origin master --follow-tags && npm publish
Or just make this part of the prepublish step.
prepublish
The main reason we can use this new method is because we don't keep the generated files in the repo anymore.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The release process right now is cumbersome af. Right now, we have to:
But wait...the changelog doesn't get updated!
I say we simplify this using
standard-version
at all times (we already refer to it in various files as the guideline for commits). This way we can:standard-version -s "chore(release): %s"
which will bump version, create a commit, create a tag, update changeloggit push origin master --follow-tags && npm publish
Or just make this part of the
prepublish
step.The main reason we can use this new method is because we don't keep the generated files in the repo anymore.
The text was updated successfully, but these errors were encountered: