Currently, as soon as we merge code to master, it gets uploaded as the latest Docker image. This means that anyone using the v1 tag will automatically start using it. Expected.

If we have customers using specific versions, they would also start using the latest Docker image. Not expected.

As part of the release process, we should also update the Docker tags. For instance, for release v1.3.0 we should have v1.3 and v1.3.0 Docker images.

As part of the release process, we would then manually trigger a GH workflow that would also publish a v1 Docker image.

@mattgauntseo-sentry does this make sense to you?