Drop 3.13t builds from cibuildwheel configuration

[ngoldbaum]

Description

See the note at https://cibuildwheel.pypa.io/en/stable/changelog/#v341 and pypa/cibuildwheel#2787.

This option will be removed in the next release of cibuildwheel. It is only needed to produce 3.13t wheels; 3.14t and future free-threaded wheels happen without any special configuration.

According to the 0.5.0 release notes, 3.13t support is already dropped.

I'm going through repositories on GitHub that enable this option and sending in PRs to disable it. Happy to answer questions about this.

If you're curious why 3.13t support is going away so soon, see https://py-free-threading.github.io/ci/#building-free-threaded-wheels-with-cibuildwheel for further guidance.

Checklist

• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[leofang]

@rwgk it seems the automation applied the label but mistakenly removed it right away:

[leofang]

This change should have triggered the red label.

(Sorry, Nathan, nothing wrong on your side, it's just that we can't accept any external contribution touching files under cuda_bindings/ and cuda_python/ directories, and in the past few days we've been tweaking the automation to make sure we can catch such events.)

[rwgk]

@rwgk it seems the automation applied the label but mistakenly removed it right away:

I just posted my best guess as to what happened: issue #1967

[rwgk]

Closing in favor of PR #1968

Thanks @ngoldbaum for the heads-up!

[leofang]

(sorry for noise, I am using this PR to debug a race condition.)

[leofang]

(nvm, the label showed up after refreshing the page...)

[leofang]

Now this looks more like a real race condition (in the opposite direction):

In a clean state (no labels):

• I manually add Need-Review label
• I then re-ran the labeler workflow right away
• the labeler workflow correctly added cuda.core/cuda.bindings labels, but they are not actually written to the database
• the net result is, as of now, only the Need-Review label survives

[cpcloud]

This was addressed in #1968.