Skip to content

1.7.0 (#482)

1.7.0 (#482) #41

Triggered via push October 26, 2023 21:03
Status Success
Total duration 48s
Artifacts
build_and_publish_pypi_and_release  /  tag_release
8s
build_and_publish_pypi_and_release / tag_release
build_and_publish_pypi_and_release  /  build_and_publish_pypi
38s
build_and_publish_pypi_and_release / build_and_publish_pypi
Fit to window
Zoom out
Zoom in

Annotations

3 warnings and 1 notice
build_and_publish_pypi_and_release / tag_release
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build_and_publish_pypi_and_release / build_and_publish_pypi
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
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
build_and_publish_pypi_and_release / build_and_publish_pypi
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/