-
Notifications
You must be signed in to change notification settings - Fork 26
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
Switch to PyPI Trusted Publishing, and remove twine #212
Conversation
PR marked as draft, so it doesn't get merged before someone enables trusted publishing on PyPI |
99% sure trusted published was enabled for this repo, but not sure how to check. |
Just run it and see, no big deal if it fails! |
it's enabled. |
loss aversion is powerful stuff. 😂 |
CI tests failing, a fix is in progress here: #214 |
😆 thanks for this! Interesting read :) |
PR #218 should fix the ruff CI errors |
@alisterburt did you pass the test? I am sad to admit that I was one of the 77% of chumps who confidently guessed powers of 2 after a bunch of positive tests. 😬 The crazy thing is that I consciously think about that test/article often, but still suffer from it. I'll spend so much time setting things up just-so, even when there is literally no cost to failure. But I deeply don't want the computer-says-no message! Stupid brain! 🧠 😂 |
@GenevieveBuckley wanna merge in main? 🙏 Then this should be ready to go in! 🚀 |
Ready to merge when the CI checks are all green. |
Closes #211
This PR switches to PyPI deployment with Trusted Publishing (see the announcement and how trusted publishing works). It removes twine, and also removes the need for PyPI API tokens being used as github secrets.
This PR is not sufficient on its own, someone else also needs to: