Build and publish #56
Annotations
5 warnings
Upload Release Assets to PyPI
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.
|
Upload Release Assets to PyPI
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
|
Upload Release Assets to PyPI
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):
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, softprops/action-gh-release@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "artifact".
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/
|
Loading