The 2.17.0.rc3 release is out, how do I backfill i...
# development
h
cc @bitter-ability-32190
b
I suspect for older branches we need to hand-hold a few things. I'll look into it later today
We can look into hand-picking them back
f
relatedly, does the "What's New" section in it need updates?
(There is some time lag between when I wrote the What's New text and when I landed the PR.)
b
It was edited by copying the contents from the changelog. We can continue editing as we change the source file.
h
I added a little bit into it
b
Oh I remember why I didn't CP. The CP doesn't work because we didn't CP the move from
build-support
to
src/pants_releese
f
also feature request for the automatic CP: it would be nice if adding "needs-cherrypick" after the PR has merged also triggers the workflow
the GitHub Actions event will be "labelled" in that case
b
(We're off topic. I'll reply in another topic 😉)
OK @happy-kitchen-89482 PR for manual CP back to 2.17.x: https://github.com/pantsbuild/pants/pull/19604
🙏 1
I don't see a way to do this easily for 2.16.x. So We'll just manage that release manually and let 2.17.x+ ride the wave
I've manually uploaded the wheels by downloading them from PyPI