Repository navigation
build: upload python wheels for 3.2.* - #5572
Conversation
There was a hard-coded "only upload the wheels to pypi for 3.1.* or 3.0.* tags." Now that 3.2 is the main release, add it. And remove 3.0, we don't need to keep building python releases for it. Signed-off-by: Larry Gritz <lg@larrygritz.com>
|
I know this is only going to be a once-a-year thing with every minor release (only if we forget to make the kind of change this PR makes), but this, to me, seems like a textbook example to include in the release skill. You could ask Claude to amend the existing prepare-patch-release skill to include a check for this kind of issue so that it never slips our minds. One caveat is that it wouldn't run at the minor release itself, but it would catch the issue at the first patch release after. |
|
I had my minion go scout the git history to find out whether this had ever happened in the past, and it reported that it happened for the 3.1 release as well. And Zach even makes a note about it in #4937. |
…t forgotten in the future Signed-off-by: Larry Gritz <lg@larrygritz.com>
Good suggestion. PR is amended. |
2 participants
There was a hard-coded "only upload the wheels to pypi for 3.1.* or 3.0.* tags." Now that 3.2 is the main release, add it. And remove 3.0, we don't need to keep building python releases for it.