Do you want to separate it from #20945?

This is to the release branch, #20945 is to main, they need to be separate, or am I missing something @glemaitre 😁

Whoops, I did not see the branch of course :)

So this passes all the wheel builds, but I don't know where to get the wheels generated by travis

Instead of Travis, we should merge #20711 for the ARM wheels.

But this should be the part to check where it is in Travis: https://github.com/scikit-learn/scikit-learn/blob/main/build_tools/github/check_wheels.py#L23-L30

So this passes all the wheel builds, but I don't know where to get the wheels generated by travis

The wheels generated by Travis are uploaded to Anaconda cloud weekly for the main branch or when a pull request is merged into a branch with the commit message marker [cd build].

AFAIK, I think that we cannot get the Travis wheels for a particular PR.

CC @thomasjpfan or @ogrisel.

Yes we can only fetch the wheels generated by the merge commit to the 1.0.X branch as the anaconda.org secret upload tokens are not available on commit triggered by a PR from a fork for security reasons.

But if the [cd build] jobs passes on the PR, they are very likely to also pass on the merge commit it-self.

BTW, I am currently working on finalizing the #20711 to get a working staging area upload step fro the linux ARM wheels on circle ci.

I rather not wait for @20711 for the release. I'll try to get an RC out today, even if it doesn't include ARM wheels (hopefully it will, from travis)

I found a way to make the travis build work faster and without failure on main: #20958.