Automate the release process with a GitHub Actions workflow #517
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
To make it easy to make releases, automate the process via GitHub
Actions.
Create a workflow that:
1. Runs cargo publish
2. Pushes a git tag,
but only if the publish was successful.
3. Creates a GitHub Release with release notes from CHANGELOG.md,
but only if creating the tag was successful.
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 is v2 of #514 that I didn't want to force push to in case we want to use the v1 workflow at a later point.
In this version the starter of the workflow provides the (masked) cargo publish token so that it does not have to be stored on GitHub.
See the other PR for more info.