Skip to content
Triggered via release January 8, 2024 11:15
@mvdbeekmvdbeek
created v1.0.5
Status Success
Total duration 43s
Artifacts

publish.yaml

on: release
Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
35s
Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
Fit to window
Zoom out
Zoom in

Annotations

5 warnings and 2 notices
Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
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/
Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
Input 'repository_url' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `repository-url` instead.
Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
Input 'skip_existing' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `skip-existing` instead.
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
Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
Using a user-provided API token for authentication against https://test.pypi.org/legacy/
Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/