Enable test.pypi.org upload

[lesteve]

Uncomment the relevant section to allow testing uploading on test.pypi.org.

[ogrisel]

Let's test this!

[lesteve]

The manually triggered workflow to watch is: https://github.com/scikit-learn/scikit-learn-release/actions/runs/33491499172

Note this take a while, probably because we have 5 macOS concurrent runners and both the PR CI + main CI + manually triggered CI needed to run.

There are 7 CI builds (Python 3.11-3.15 + 2 free-threaded) * 2 (macOS Intel + macOS arm) * 3 (PR CI + main CI + workflow_dispatch) = 42 (the answer to the Ultimate Question of Life, the Universe, and Everything 😉). No wonder it is taking a while.

[ogrisel]

So next time we should not forget to cancel the runs we don't care about.

[lesteve]

The macOS Intel also are quite slow (25-30 minutes) https://github.com/scikit-learn/scikit-learn-release/actions/runs/33491499172 but it's the same on the scikit-learn repo https://github.com/scikit-learn/scikit-learn/actions/runs/33467476903, so not related to the scikit-learn-release repo.

The last macOS Intel on Python 3.15 free-threaded is over 32 minutes and only at 60% of the tests https://github.com/scikit-learn/scikit-learn-release/actions/runs/33491499172/job/99803801107 😓

For completeness non-macOS Intel builds are more 10-20 minutes.

[lesteve]

The wheels have been successfully uploaded to test.pypi.org worfklow log + test PyPI release.

I thought there would be some manual approval where we would have to click a button but no. Maybe this only happens when uploading to PyPI not testPyPI?

[ogrisel]

I cannot see any manual confirmation step in the wheels.yml workflow file.

[ogrisel]

The last macOS Intel on Python 3.15 free-threaded was 45 min. The same build on macOS arm64 is less than 15 min as the other build. So it's probably not a problem of CPython 3.15 or free-threading but rather that the macOS Intel runners are overloaded...

[lesteve]

I triggered another one manually
https://github.com/scikit-learn/scikit-learn-release/actions/runs/33525961034

to:

• see what happens if a wheel has been uploaded already, I think skip-existing: true will not upload new wheel and the workflow will succeed
• to test the required reviewers functionality where we have to click a button to allow the upload: https://github.com/scikit-learn/scikit-learn-release/settings/environments/16619784573/edit. For now I have manually set @ogrisel, @jeremiedbb and @lesteve.

[jeremiedbb]

to test the required reviewers functionality where we have to click a button to allow the upload

I approved, which triggered the upload to testpypi. 🎆

I think skip-existing: true will not upload new wheel and the workflow will succeed

Skipping scikit_learn-1.10.dev0-cp311-cp311-macosx_10_9_x86_64.whl because it appears to already exist

the workflow succeeded 👍

[lesteve]

Nice, I was also wondering "where we can we see who approved the workflow manually?" and it took me a while to find it so you need to search for "Deployment Protection rules" towards the bottom of the workflow run log