Pato Sandaña

@epage do you have a "workflow" in mind to combine GitHub Releases, GitHub Actions and the usage of Cargo Release? Maybe worth document it, as someone can automate the creation...

@epage, is there a way to create annotated tags instad of lightweight tags?

> They should be annotated; we pass `-a` False alarm. I was not pushing the tag, but later using `gh release` which added a non-annotated tag. Thanks for the support.

> [@wiktor-k](https://github.com/wiktor-k) Does `cargo llvm-cov run --no-report` + `cargo llvm-cov report` not work? > > If you want to do something like `cargo llvm-cov run --no-run`, show-env mentioned above is...

> Thanks, Also, I think I added a workaround for the "binary files differ" failure, which should be removed as it will no longer be necessary. Martin There are more...

@sourcefrog maybe I misunderstood. Do you want me to do these changes on this PR? > Specifically [78b7e31](https://github.com/sourcefrog/cargo-mutants/commit/78b7e313a4f3cc9bab504ca5d643c0ce3d9ce7a9) could be partially reverted, leaving the test in place, and the changelog...

@sourcefrog I partially reverted [78b7e31](https://github.com/sourcefrog/cargo-mutants/commit/78b7e313a4f3cc9bab504ca5d643c0ce3d9ce7a9). Is anything left? :)

FYI, due the lack of releases in the project, forks are starting to spawn: https://crates.io/crates/criterion2

You can store the secrets in GitHub, and make a release pipeline that only triggers on GH releases (pushed tags), so you get releases from the pipeline, not humans locally.

After 2 years, fixed with #860 . Thank you!