added release-plz config #912
Merged
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
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.
The release-plz action
We recently started using this to automate our semantic versioning after it was recommended by the nior-lang team. It has been a large quality of life improvement and improves stability. When done manually, semantic versioning is error prone and these errors can lead to problems in down-stream dependancies. If configured this will run on every PR into main and detect semantic versioning changes, it will then open a PR with a release tag, changelog, and auto incremented semver (under the hood this is done with cargo-semver-checks).
This is incomplete as only the repository administrator can configure the github token as well as the cargo registry token.