Automate releases #467
Merged
Automate releases #467
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
noelia-lencina
approved these changes
Mar 11, 2021
There was a problem hiding this comment.
Very nice work! 🙌
To confirm I understood this correctly, the process of releasing a new version will be:
- Commit your changes and open PR for review.
- Once that's merged into master, use prep-release to patch de version.
- Finally, use release to create a new branch, push the branch and that will automatically release a new version.
Co-authored-by: noelia-lencina <noelia@wyeworks.com>
@noelia-lencina yes, that's correct. |
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.
Currently, new releases have to be perform locally, this has brought us troubles in the past where the person with permissions didn't have the local env set so the binaries had to be proxy by someone else from the team what ended up with some versioning problems.
In order to avoid this situations, the aim of this work is to automate the releasing process so the binaries for new versions get deploy automatically. Also, some users have been requesting to publish binaries along with the GH release so the can download them directly from GH, this work also addresses this request.
The releasing process has been detailed in the readme.