FYI. Now that release prep is always done on the b...
# development
b
FYI. Now that release prep is always done on the branch itself. I'm turning on branch protection for every release branch 🙂 Thanks for playing ❤️
❤️ 2
FYI @witty-crayon-22786. No more two-PRs 😛 Finally.
For posterity I implemented this as a ruleset, so I could enforce one setting across
main
AND the release branches (otherwise with the "old school" rules, you have to duplicate the settings)
c
could wait until 2.16 and 2.17 are done, perhaps?
b
No, you should bump the version in that PR. This is now called out on the docs with my two latest PRs 😛 https://github.com/pantsbuild/pants/pull/19896 https://github.com/pantsbuild/pants/pull/19895
c
and have them auto-picked to the release branches then?
but wait, mr PRs are for
main
to update the notes...
don't want to bump VERSION there
b
Oh hmm
I totally missed that
Do we really need those on
main
anymore?
c
maybe not any more... but feels weird to stop mid release branch.
b
The https://www.pantsbuild.org/docs/changelog page could just point to the release branch. And we can always recreate form the releases.
c
feels better to keep doing it for 2.17 at least, then I guess we could not for 2.18
b
maybe not any more... but feels weird to stop mid release branch.
True. OK
(We already don't for 2.18)
c
yea
ok
b
OK so I disabled https://github.com/pantsbuild/pants/settings/rules/96431 Luckily it still sticks around
c
cool, guess we can just enable it again once we're done with the <=2.17 releases
b
yee
c
about to hit bed, will pick and run the final step for those releases tomorrow.