-
-
Notifications
You must be signed in to change notification settings - Fork 26k
CI Use right environment in Pyodide wheel upload #31078
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks, @lesteve!
Keeping environments fine-grained is nice, but it also causes a maintenance burden. Leaving it up to y'all to decide. :) |
I think it's fine to reuse this env. |
Maybe @adrinjalali or @thomasjpfan for a second opinion on the security aspect of sharing the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm okay with reusing this environment for WASM wheels.
OK thanks, let's merge this then! |
Manual workflow now running at: https://github.com/scikit-learn/scikit-learn/actions/runs/14088599788 🤞 |
Pyodide wheels are on anaconda.org 🎉 https://anaconda.org/scientific-python-nightly-wheels/scikit-learn/files. |
Follow-up of #29791 after the upload fails #29791 (comment) because the token is empty.
Not sure if we should use the same environment or if we should have a separate environment for the main wheels upload and the Pyodide wheel upload. In particular the Pyodide wheel upload only needs
SCIKIT_LEARN_NIGHTLY_UPLOAD_TOKEN
and notSCIKIT_LEARN_STAGING_UPLOAD_TOKEN
. cc @ogrisel.