updating requirements and pypi release #14
taklinepublish-to-pypi.yaml
on: push
test
1m 30s
Sign the Python 🐍 dist 📦 with Sigstore and upload them to GitHub Release
20s
Publish Python 🐍 distribution 📦 to PyPI
34s
Annotations
1 error and 7 warnings
|
test
Process completed with exit code 1.
|
|
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Build distribution 📦
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Sign the Python 🐍 dist 📦 with Sigstore and upload them to GitHub Release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "coverage-results", "python-package-distributions", "test-results".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
|
Publish Python 🐍 distribution 📦 to PyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. 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):
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
coverage-results
|
41.1 KB |
|
|
python-package-distributions
|
55.3 KB |
|
|
test-results
|
5.41 KB |
|