ci: add release-plz config file
#57
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
sripwoud
force-pushed
the
ci/release-plz
branch
from
d394425
to
63d80fa
Compare
https://release-plz.ieni.dev/docs/config#the-release_commits-field diff --git a/.release-plz.toml b/.release-plz.toml new file mode 100644 index 0000000..d97699d --- /dev/null +++ b/.release-plz.toml @@ -0,0 +1,2 @@ +[workspace] +release_always = false
sripwoud
added
bug 🐛
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.
Attempt to address #55 (comment)
Maybe what happened is:
release_alwaysis by default true so therelease-plzCLI runsrelease-prcommand (updatecommand AND opening of PR): it tries to update but failed (e.g. no pkg on crates.io and no CHANGELOG file yet, see https://github.com/privacy-scaling-explorations/zk-kit.rust/actions/runs/11124754559/job/30910962049#step:4:230). A PR is opened nonetheless.releasecommand: runs nonetheless, new crate is publishedrelease-prstep that includes theupdatecommand detects a new commit (the PR merge at step 1) and bumps the version again, creating a new PR too.A fix could be to set
release_alwaystofalse.