Currently the process of adding a new release branch is not really defined.
It is possible to create an empty branch and let the automatic discovery create many PRs for all the watched plugins, but then it would be required to manually reintegrate the manual changes to the overlay that were added and merged in the previous release branch.

There are mainly 2 options here:

• Create the next release branch based on the previous release branch merged content (creating a PR in the next release branch for each merged content of the previous release branch and updating the reference commit in one go)
• switch to a model where we have a release-main branch where most manual additions occur, and at a given point in time, create the next release release branch based on it, according to a process and with guardrails which are still to be defined.