-
Notifications
You must be signed in to change notification settings - Fork 107
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
Update wheel.yml to build ARM wheels and switch to trusted PyPi upload rather than using a token. #1298
Conversation
Note also that I followed your lead in removing python 3.7 from our list of wheel builds. |
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 think there's at least one bug. But mostly just have to try this and see.
@@ -75,10 +106,16 @@ jobs: | |||
# Just need to build sdist on a single machine |
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 think you'll need to update the above to
needs: [build_linux_wheels, build_musl_wheels, build_macosx_intel_wheels, build_macosx_arm_wheels]
.github/workflows/wheels.yml
Outdated
build_macosx_wheels: | ||
name: Build wheels on macosx | ||
build_macosx_intel_wheels: | ||
name: Build wheels on MacOS Intel | ||
runs-on: macos-latest |
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.
You might need to change this to macos-13 to get an intel runner. It's possible an ARM runner will cross-compile though, just need to try and see I guess.
Thanks! I think you're right on both counts. |
In preparation for releasing version 2.5.3, I added arm wheels to our wheels.yaml script.
Also, PyPi now prefers using trusted publishing. (cf. https://docs.pypi.org/trusted-publishers/adding-a-publisher/) So I switched to that as well.
This is hard to confirm before actually running the script, which will happen when we make the release tag v2.5.3. But @jmeyers314 if you can look through it once to see if there are any errors that you can notice in advance, that would be appreciated.