Automate release process using semantic-release #77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This allows semantic-versioning to be able to properly increment the version number.
Zip file package now gets created in dist folder. Version number in manifest.json is now passed in as an argument.
GitHub already provides a link to compare previous releases, so we don't need to add it
this enables semantic release to commit both of those files with updated version numbers whenever a release occurs
mnunemacher-dm
approved these changes
May 11, 2020
yutingcxiang
approved these changes
May 11, 2020
|
🎉 This PR is included in version 1.7.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR automates the release process using the semantic-release library. Fixes #71
When a PR is merged to the master branch and the tests pass, the semantic release library will create a new GitHub release with release notes and a zip file for the Chrome Web Store attached. Publishing to the Chrome Web Store is still a manual step -- that will be done in #72.
All commit messages are now required to follow AngularJS's commit message convention. I've configured Commitizen and husky to enforce this and provide assistance in writing proper messages.
There is support configured for releasing first to a beta branch, but we haven't been able to get beta publishing to work in the Chrome Web Store, so this feature is currently disabled.