Repository navigation
[Bot] Update dependencies - #3003
Conversation
|
hm. so the 3.15 final delay presents a little conundrum - are we okay to wait for 3.15 final for our next v4.3 release? It would be nice for 3.15 final to coincide with a feature release of cibuildwheel IMO. The downside is we don't put out a release of cibuildwheel with this rc3. I think that would be okay since rc1 is the main milestone for cibuildwheel. so options are: a) cherry pick 3.15rc3 onto a minor version branch and put out a cibuildwheel v4.2.2 version soon my feeling is (c) - any objections? |
|
my feeling is (b) |
|
Any one of those are fine with me, though I like (b) best. There shouldnβt be any actual difference between the final and RC. |
|
Asked Claude to check on my phone, looks like we have never lined up a final release with a minor bump, always patch. π€ AI text below π€ No β every final
The minor bump has always gone with RC1, when the new Python starts building by default. For example, v4.2.0 made CPython 3.15 wheels build by default with 3.15.0rc1, matching v3.1.0, v2.20.0, v2.15.0, v2.9.0 and v2.1.1 in earlier years. The release just before Sources: |
|
Thanks for the input - on reflection I agree with you guys. I'll do the release now. |
Update the versions of our dependencies.
PR generated by "Update dependencies" workflow.