**Goal:** the release process is smooth. Everything that can be automated is automated. Steps are clear. New engineers could also follow it with minimal training or supervision.
**Context:** the current release process is fully manual and cumbersome (see T332786). That makes is too time consuming and prone to errors and overlooking things. Threshold for new engineers to step it is also too high. Confidence that we are doing it right is usually low.
**Open Question:**
- Check for the "latest" tag. What should we tag as the "latest" release?
**Acceptance Criteria:**
Write tickets to automate the release process
Some tickets may hypothetically be:
[] script for the creation of the needed env files with the needed variables
[] script that checks the last commit hashes of the different extensions, till we get to the point that everything is done for us and we just need to do the last checking :boom:
[] store the commit hashes to ensure reproducibility of the releases, see also T340226
[] create make target for dockerhub publish