release-plz: Don't immediately publish new crates to crates.io
Motivations
Most of my projects consists of workspaces with more than 1 crate. When I add new crates to these, release-plz will immediately try to publish to crates.io (for those new crates) without going through the release PR.
- Would you like to implement this feature? [y/n]
Solution
release-plz should wait to release the new crates til the release-pr is merged (changelog is generated etc.)
Alternatives
Additional context
About this issue
- Original URL
- State: closed
- Created 4 months ago
- Comments: 18 (9 by maintainers)
I don’t run cargo publish by myself. It happens in the same github action that runs release-please. But sure, the semver violation checks are definitely one of the reasons I’m trying out release-plz for my projects. That and some rust-related issues I’ve had with release-please.
I meant it isn’t part of https://release-plz.ieni.dev/docs/github/quickstart which i think is dangerous as a guide. Will look into the pr process you use. going from the defaults i did not get the flow i was hoping for yet.
PS: The donation is just a coffee or two for your time 😃