Improve releasing

[hdevalke]

Currently releasing is done manual.
This process could be automated using a github action.

Manual steps:

1. running cargo release $(convco version --bump) --execute on the master branch (needs git access and crate io credentials)
2. download all binaries from the Build binary action
3. create a new release from the tag pushed by (1)
4. upload all downloaded artifacts from (2)

[taorepoara]

In my opinion creating the release should not be part of this project since it's easy do them manually. A simple doc guide should be enough.

I think that what make convco great is it minimalism.

If you start manage GitHub releases, why don't you manage GitLab releases, and then why don't you manage other things with plugins, and boom, you're just a Rust Semantic Release...

[hdevalke]

Thanks for your input. This is more about releasing convco itself then releasing applications using convco. It is not the goal to add a convco release sub command.

The main goal is to make it less time consuming for myself to release convco

[taorepoara]

Oh sorry for my misunderstanding ^^
Here is one of our GitHub action file for a Rust CLI to get inspired: https://github.com/lenra-io/lenra_cli/blob/main/.github/workflows/build_ci.yml

We are not using convco yet (because we have lot to do), but it could help you creating your own.

[hdevalke]

A manual workflow has been added to trigger a release.
It does run cargo-release and creates a new tag (0.5.1 has been released this way)
However, the build binaries workflow does not trigger automatically.

So next steps:

• trigger build binaries
• improve build binaries workflow to also create a release in case it was not manually triggered