Feature request: post-release-hook

[Person-93]

Is running a post release hook within the scope of this project? I see that it's mentioned here as something that might be considered. Would you accept a PR that implements it?

My use case is to push additional git tags. If the new version is 2.6.22, I'd want three tags applied to that commit: v2, v2.6, and v2.6.22. The last one is already handled by cargo-release, but I'd like to add some custom logic at the end of the process for the other two tags.

[epage]

post-release hook sounds reasonable.

[psandana]

@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 of tags starting from GitHub Releases.

[epage]

We have a FAQ entry for that: https://github.com/crate-ci/cargo-release/blob/master/docs/faq.md#how-do-i-automate-creating-a-release-on-github

[psandana]

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

[epage]

They should be annotated; we pass -a

[psandana]

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.