Mark next version post release with -SNAPSHOT

[jnioche]

Bug description

The version in the cargo files is currently showing 3.1.0 which has already been released.
What we should do instead if to move to the next version right after a release and suffix it with -SNAPSHOT
We should make this explicit in any documentation we have about the release process

[jnioche]

@demeringo is the release process documented anywhere?

[demeringo]

@jnioche No this release process is not documented, but it certainly should !

The current semi manual release process involves:

• updating cloud scanner version in the cloud-scanner-cli cargo.toml https://github.com/Boavizta/cloud-scanner/blob/main/cloud-scanner-cli/Cargo.toml
• updating the version in cloud-scanner-lambda cargo.toml: https://github.com/Boavizta/cloud-scanner/blob/main/cloud-scanner-lambda/Cargo.toml
• updating the tag of the image in docker-compose (using the not-yet-published version that we declared just above)
• updating the changelog.md (mention this new version, move unreleased entries under this new version)
• merge this changes to main
• create a github relase vX.Y.Z (i.e. in practice, this will tag the main branch with the tag 'vX.Y.Z` when the release is published), I generally tick the option to create a related discution in github https://github.com/Boavizta/cloud-scanner/discussions
• publish the release (which triggers the tagging, and consequently the build / publish of docker image in CI).

Sometimes, if I fear a breaking change, I publish an -alpha or -beta release (like https://github.com/Boavizta/cloud-scanner/releases/tag/v2.0.0-alpha) and mark it as a pre-release in github, but generally not.

[demeringo]

And yes, I fully agree with adding systematically the -SNAPSHOT tag to avoid confusion with published versions.

[jnioche]

thanks @demeringo , I copied your comments to

https://github.com/Boavizta/cloud-scanner/wiki/Release-Process

to make it easier to find later

[jnioche]

@demeringo why not just rely on

image: ghcr.io/boavizta/cloud-scanner-cli:latest

in docker-compose?