Skip to content

Publish 2.2.0@fa91ca80880b30d4f8cf5b59ec73bf6b87cf0931 #170

Publish 2.2.0@fa91ca80880b30d4f8cf5b59ec73bf6b87cf0931

Publish 2.2.0@fa91ca80880b30d4f8cf5b59ec73bf6b87cf0931 #170

Triggered via push September 24, 2026 18:40
Status Success
Total duration 1m 27s
Artifacts 2

publish.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

4 warnings and 2 notices
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.
build
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
publish
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

Artifacts

Produced during runtime
Name Size Digest
dist
552 KB
sha256:3cc503c20bcf2d175a79837d3e7ff066dbe96d09517818b9e2ee2cb113a728bd
dist-handoff.tar
560 KB
sha256:16846707bca93bc2e54bd2a2a62e36c3d567d303dac110a5538da80fd890c2f2