chore: update to cargo-dist 0.10.0 and use standard cargo-dist release script #85
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.
Upgraded to cargo-dist 0.10.0
cargo dist init
generatesWhat I've tested:
Sample PRs generated by prepare-release.yml:
Here is a workflow run that shows what happens if you don't specify a version:
What I haven't tested:
I haven't tested merging a release PR to main and running the
cargo release
command from the PR description.That being said, since we're using the stock cargo-dist release workflow now, we can have confidence that the standard release process would work: updating the crate version on main (which merging the release PR would do) and pushing a tag. The prepare-release.yml workflow and
cargo release
just make that slightly more convenient.