Skip to content

Update setup.py (#37) #3

Update setup.py (#37)

Update setup.py (#37) #3

Triggered via push January 7, 2024 00:20
Status Success
Total duration 2m 26s
Artifacts

release.yml

on: push
Matrix: ciPython310
Matrix: ciPython37
Matrix: ciPython38
Matrix: ciPython39
Build and publish Python 🐍 distributions 📦 to PyPI
48s
Build and publish Python 🐍 distributions 📦 to PyPI
Fit to window
Zoom out
Zoom in

Annotations

5 warnings and 1 notice
ciPython39 (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
ciPython310 (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
ciPython37 (3.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
ciPython38 (3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: 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 Python 🐍 distributions 📦 to PyPI
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/