The README says the last step of the workflow is to:
switch default repository branch to newest release branch
I think it’s not actually the last step, it looks like there are 2 steps after that: https://github.com/laminas/automatic-releases/blob/2008a9e98f65c0dcacb90eabb4d12987080ed1d7/examples/.github/workflows/release-on-milestone-closed.yml#L49-L67
Anyway, I’d like to know if it is possible to avoid switching the default branch to the next minor branch, but still create it if it does not exist. For instance when releasing
doctrine/orm 2.8.0, I expect branch
2.9.x to be created, but I don’t expect to switch to it. See this discussion for why that switch is not necessarily something we want.