Currently, we need to update the crate/package version in Cargo.toml by hand to create a new release. It would be nicer to have the release GitHub action inject the crate/package version based on the pushed tag rather than having to remember to update the version before creating a new release.
Unfortunately, in contrast to poetry, neither cargo nor maturin have a command to do so out of the box. We could probably engineer a GitHub actions step using cargo-edit (https://github.com/killercup/cargo-edit) to inject the desired crate/package version in the release workflow.
Context
Currently, we need to update the crate/package version in
Cargo.tomlby hand to create a new release. It would be nicer to have the release GitHub action inject the crate/package version based on the pushed tag rather than having to remember to update the version before creating a new release.Unfortunately, in contrast to
poetry, neithercargonormaturinhave a command to do so out of the box. We could probably engineer a GitHub actions step usingcargo-edit(https://github.com/killercup/cargo-edit) to inject the desired crate/package version in the release workflow.Alternatives
Do nothing