cargo-release: pre-release-commit-message template replacements don't seem to work

Hi there!

I’m trying to adapt cargo-release to work for nextest. The nextest workspace consists of several crates, each with their own independent versioning.

If I’d like to update one of nextest’s crates, I’d like to be able to do:

cargo release -p nextest-filtering 0.2.2 --execute

and have a commit be created with the requisite version bumps and the message:

[nextest-filtering] version 0.2.2

and a signed tag created on this commit called nextest-filtering-0.2.2 with message:

nextest-filtering version 0.2.2

Here’s my first attempt at configuring that, based on the reference:

https://github.com/nextest-rs/nextest/blob/main/release.toml

However, when I run:

cargo release -p nextest-filtering 0.2.2 --execute

the commit that gets created is:

commit 49aaac68f9fae149b957ed79508e3551cd20d816 (HEAD -> main)
Author: Rain <rain@sunshowers.io>
Date:   Fri Oct 14 12:23:50 2022 -0700

    [{{crate_name}} version {{version}}

which indicates that template replacements aren’t working.

Any idea how to make them work?

% cargo release --version
cargo-release 0.21.4

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (5 by maintainers)

Commits related to this issue

Most upvoted comments

Also, you might be able to replace release-publish.toml with cargo release publish --publish

--publish is telling the cargo release publish command to override the config and do a publish anyways. Its not a --force because I kept the flags the same between cargo release and the step subcommands.