-
Notifications
You must be signed in to change notification settings - Fork 36
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
Release 2024.6.20
.
#333
Release 2024.6.20
.
#333
Conversation
Populated templates via: ``` $ python scripts/doc_template_release.py Linux GitHub Actions Run ID: 9607943395 Windows GitHub Actions Run ID: 9607943396 Coveralls Build ID: 68215528 macOS GitHub Actions Run ID: 9607943397 ```
Built all wheels via: https://github.com/dhermes/bezier/actions/runs/9608025437 |
To upload, I made a [distutils]
index-servers =
testpypi
[testpypi]
username = __token__
password = pypi-Ag... I downloaded all the files and put them in a shared
depending on the "current" contents of |
As part of the upload process, I also tagged the commit and pushed the tag:
To make the actual release (https://github.com/dhermes/bezier/releases/tag/2024.6.20) in Markdown, I used
Even still it is imperfect because of line wrapping, so I manually edited the output ( |
After pushing the tag, the TestPyPI release checked out (URLs in the release refer to the tag). After this was validated, I changed [distutils]
index-servers =
pypi
[testpypi]
username = __token__
password = pypi-Ag... and then uploaded via:
depending on the "current" contents of |
Worth noting: I do not have easy access to macOS hardware running 10.9 (x86_64) or 11.0 (arm64). As a result, the only macOS wheels I built were on the This may be an issue for macOS users on earlier versions. If someone has a request for earlier versions and hardware, I can likely help collaborate with them to get wheels built and uploaded to PyPI. The biggest blocker to this is actually getting a version of
See I actually considered using old versions of the |
Populated templates via:
I'll be using this PR to post comments about the release process (for audit purposes).
See also #309 and #330