The new automated release process is in place (completed with #10233). I made sure that the existing manual process still works.

Even if I extensively tested the new process on a fork, there might be some aspect to refine (GitHub token permissions, ...). For this reason, I propose to be the release manager for a future version of Haystack.

Based on the above considerations regarding compatibility, it is not mandatory that it be version 2.22.0. If I am unavailable, we can still use the old process.