Integrate release-plz to automate release & crate publish
#224
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
Signed-off-by: Anthony Griffon <anthony@griffon.one>
|
Currently there are multiple crates in this repo, do you have ideas for publishing them separately? |
|
You can publish them separately with |
|
Hi, @Miaxos thank you a lot for raising this PR first. However, I personally feel that we don't need this action right now given our current low frequency of releases. How about let's close this PR and rethink about it in the future? |
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.
Following #223 this is the corresponding workflow needed to integrate it.
For the tokens creation and set up of the whole things, you'll need to refer to this: https://release-plz.ieni.dev/docs/github/token