Skip to content
Triggered via release October 14, 2024 16:08
@ZihengSunZihengSun
published v1.1.3
Status Success
Total duration 1m 39s
Artifacts

publish-to-pypi.yml

on: release
Matrix: Test Python Installation for 3.8, 3.9, 3.10, 3.11
Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
40s
Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Test Python Installation for 3.8, 3.9, 3.10, 3.11 (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Python Installation for 3.8, 3.9, 3.10, 3.11 (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Python Installation for 3.8, 3.9, 3.10, 3.11 (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test Python Installation for 3.8, 3.9, 3.10, 3.11 (3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):