The release process right now is cumbersome af. Right now, we have to:
- bump version manually
- npm install (to get the version bump into package-lock)
- npm publish (to build/publish new version)
- commit the new files
- tag the new files
- push tag/commit out
- forget to create the actual release
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:
- run
standard-version -s "chore(release): %s" which will bump version, create a commit, create a tag, update changelog
- run
git 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 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-versionat 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 publishOr just make this part of the
prepublishstep.The main reason we can use this new method is because we don't keep the generated files in the repo anymore.