Skip to content

[Bot] Update dependencies - #3003

Merged
henryiii merged 1 commit into
mainfrom
update-dependencies-pr
Oct 3, 2026
Merged

henryiii merged 1 commit into
mainfrom
update-dependencies-pr

Conversation

@cibuildwheel-bot

Copy link
Copy Markdown
Contributor

Update the versions of our dependencies.

PR generated by "Update dependencies" workflow.

@cibuildwheel-bot
cibuildwheel-bot Bot requested a review from hoodmane as a code owner October 3, 2026 09:34
@cibuildwheel-bot cibuildwheel-bot Bot added CI: GraalPy Run the integration test suite with GraalPy included CI: PyPy Run the integration test suite with PyPy included labels Oct 3, 2026
@cibuildwheel-bot
cibuildwheel-bot Bot requested a review from ryanking13 as a code owner October 3, 2026 09:34
@cibuildwheel-bot cibuildwheel-bot Bot added CI: PyPy EoL Run the integration test suite with PyPy EoL versions included dependencies Pull requests that update a dependency file labels Oct 3, 2026
@henryiii
henryiii merged commit 5cad3d9 into main Oct 3, 2026
45 of 52 checks passed
@henryiii
henryiii deleted the update-dependencies-pr branch October 3, 2026 12:51
@joerick

joerick commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

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
b) just release our cibuildwheel v4.3.0 this week and put out a patch version with 3.15.0 final later
c) wait for 3.15.0 final and release v4.3.0 then

my feeling is (c) - any objections?

@mayeut

mayeut commented Oct 3, 2026

Copy link
Copy Markdown
Member

my feeling is (b)

@henryiii

henryiii commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

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.

@henryiii

henryiii commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

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 .0 CPython update has shipped as a patch release, never a minor bump. That supports option (b) in the thread.

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 .0 has been a mix. v3.2.0 was a minor release carrying 3.14.0rc3, while v2.16.1 and v2.21.2 were patch releases with rc3. So (b) fits the usual pattern: a v4.3.0 now with rc3, then a v4.3.1 for 3.15.0.

Sources:

@joerick

joerick commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Thanks for the input - on reflection I agree with you guys. I'll do the release now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI: GraalPy Run the integration test suite with GraalPy included CI: PyPy EoL Run the integration test suite with PyPy EoL versions included CI: PyPy Run the integration test suite with PyPy included dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants