Default branch is not being switched after a release
Ocramius opened this issue · 5 comments
Noticed when releasing https://github.com/doctrine/DoctrineMigrationsBundle/milestone/22
As I closed the milestone, the pipeline did run successfully: https://github.com/doctrine/DoctrineMigrationsBundle/runs/3941893625?check_suite_focus=true
The branch for 3.3.x was not created though.
There is some issue with the release tool, it happened the same last week with the migrations library
The step that does the switch was deliberately omitted on some repos, and not on the mongoDB ones, because of different policies regarding what the default branch should be: either the current patch or the next minor.
Right, but then 3.3.x was still not created.
Not switching default branch => OK
Not having 3.3.x is a bit more confusing, but perhaps you want to do this manually.
If that's the case, this can be closed.
Not having 3.3.x is a bit more confusing, but perhaps you want to do this manually.
I think it would be cool to have the laminas/automatic-releases step split into 2 steps, dunno how easy to do that is.
dunno how easy to do that is.
Feasible, just work to be done, and with BC of existing commands in mind.