Skip to content

Publish 2.0.0-rc.22@b74d187e44efe62a3041a0b91ef271f6a1f4b1ad from direct #143

Publish 2.0.0-rc.22@b74d187e44efe62a3041a0b91ef271f6a1f4b1ad from direct

Publish 2.0.0-rc.22@b74d187e44efe62a3041a0b91ef271f6a1f4b1ad from direct #143

Triggered via push August 9, 2026 09:29
Status Success
Total duration 4m 35s
Artifacts 2

publish.yml

on: push
publish-test
publish-test
deploy-and-audit-api-reference
3m 32s
deploy-and-audit-api-reference
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
PyPI rendered-page audit
rendered project page returned a client challenge; exact PyPI JSON remains authoritative
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.

Artifacts

Produced during runtime
Name Size Digest
dist
472 KB
sha256:be2e07641c082abf73b09594eb39e184d9cca54b5eebd388384f8d6c527451e3
dist-handoff.tar
480 KB
sha256:b0cb518fbcf6e76a8ad8d54e3d46541c31aaa975f3e5f2070bf0173cde3256f9