Skip to content
Publish Python 🐍 distributions 📦 to PyPI

Use compatible release clause ~= defined at PEP 440 (#65) #12

Sign in to view logs

Use compatible release clause ~= defined at PEP 440 (#65)

Use compatible release clause ~= defined at PEP 440 (#65) #12

Triggered via push November 5, 2024 09:45
@wd0517wd0517
pushed acfacf7
5.0.1
Status Success
Total duration 47s
Artifacts –

release.yml

on: push
Build and publish Python 🐍 distributions 📦 to PyPI
38s
Build and publish Python 🐍 distributions 📦 to PyPI
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build and publish Python 🐍 distributions 📦 to PyPI
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/
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
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):