Skip to content
Publish to PyPI

Publish 2.0.0-rc.21@fd7ca4ed3c90bc481a87097b2091c7888b1f2505 from direct #142

Sign in to view logs

Publish 2.0.0-rc.21@fd7ca4ed3c90bc481a87097b2091c7888b1f2505 from direct

Publish 2.0.0-rc.21@fd7ca4ed3c90bc481a87097b2091c7888b1f2505 from direct #142

Re-run triggered August 9, 2026 05:15
@rmcdanielrmcdaniel
fd7ca4e
2.0.0-rc.21
Status Failure
Total duration 5m 12s
Artifacts 2

publish.yml

on: push
build
29s
build
publish
5m 7s
publish
publish-test
publish-test
deploy-and-audit-api-reference
deploy-and-audit-api-reference
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
publish
Process completed with exit code 1.
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):
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
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.