chore(ci): add cargo release functionality

[okaerin]

Closes #122

Description

Change Unreleased to released and prepare a new Unreleased section.

Check List (Check all the applicable boxes)

• I understand that my contributions needs to pass the checks.
• If I created new functions / methods, I documented them and add type hints.
• If I modified already existing code, I updated the documentation accordingly.
• The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

[codspeed-hq]

CodSpeed Performance Report

Merging #130 will not alter performance

_{Comparing okaerin:cargo-release (8ead32c) with main (3dfcc9a)}

Summary

✅ 6 untouched benchmarks

[okaerin]

Hi @jeertmans as the rustfmt failure stems from the pull request #129 should I fix it here or create a separate one? And on the other hand is it how you imagined that the issue would be solved?

[jeertmans]

Hi @okaerin, thanks for your contribution!

Hi @jeertmans as the rustfmt failure stems from the pull request #129 should I fix it here or create a separate one? And on the other hand is it how you imagined that the issue would be solved?

No, #117 will address that, don't worry ;-)

Could you please document the installation / need of cargo-release?

E.g., there could be a RELEASE-PROCESS.md file that explains how to install cargo-release and how to use it to properly release a new version. I think I did this for another repo I maintain, see https://github.com/maciejhirsz/logos/blob/master/RELEASE-PROCESS.md

[okaerin]

Hi @okaerin, thanks for your contribution!

Hi @jeertmans as the rustfmt failure stems from the pull request #129 should I fix it here or create a separate one? And on the other hand is it how you imagined that the issue would be solved?

No, #117 will address that, don't worry ;-)

Could you please document the installation / need of cargo-release?

E.g., there could be a RELEASE-PROCESS.md file that explains how to install cargo-release and how to use it to properly release a new version. I think I did this for another repo I maintain, see https://github.com/maciejhirsz/logos/blob/master/RELEASE-PROCESS.md

I used the RELEASE-PROCESS.md as guidance, thanks. Any chance that we could bump the version of languagetool-rust to 2.1.5? Of course I could prepare a PR after this one.

[jeertmans]

Thanks for your contribution!

I used the RELEASE-PROCESS.md as guidance, thanks. Any chance that we could bump the version of languagetool-rust to 2.1.5? Of course I could prepare a PR after this one.

Yes, please do that in another PR :-)