Our current docker-release workflow is publishing updated docker images to dockerhub in two cases:

• when we merge a PR on main, publishing the image with the main tag
• when we publish a release, publishing the image with the release tag (eg v0.1.0)

This is forcing us to update the instructions for guiding users in running the latest most stable version of this project every time we're gonna ship a release, which is not ideal.

The best thing would be to keep publishing the versioned image + overwriting a dedicated latest/stable tag, which is gonna be the one mentioned in every kind of documentation and instructions.

My proposal is to have this final structure moving on:

• main tag --> reflecting the latest main branch status
• latest/stable tag --> reflecting the latest stable release
• v0.1.0 tag
• v0.2.0 tag
• etc