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

Add standard version as part of the release process #210

Open
AntJanus opened this issue Oct 12, 2018 · 0 comments
Open

Add standard version as part of the release process #210

AntJanus opened this issue Oct 12, 2018 · 0 comments
Milestone

Comments

@AntJanus
Copy link
Collaborator

The release process right now is cumbersome af. Right now, we have to:

  1. bump version manually
  2. npm install (to get the version bump into package-lock)
  3. npm publish (to build/publish new version)
  4. commit the new files
  5. tag the new files
  6. push tag/commit out
  7. 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:

  1. run standard-version -s "chore(release): %s" which will bump version, create a commit, create a tag, update changelog
  2. 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.

@AntJanus AntJanus added this to the next release milestone Oct 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant