Skip to content
Publish to PyPI

v3.9.6 #63

Sign in to view logs

v3.9.6

v3.9.6 #63

Triggered via release November 13, 2023 13:20
@NekoAriaNekoAria
published v3.9.6
Status Success
Total duration 54s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

release.yml

on: release
Matrix: deploy
Fit to window
Zoom out
Zoom in

Annotations

4 warnings and 4 notices
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
deploy (3.11)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
deploy (3.9)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
deploy (3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
deploy (3.8)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/