Skip to content

Publish 2.3.8@e02afd2ad49708ea9cb5bf84f9f5603d208b973a #179

Publish 2.3.8@e02afd2ad49708ea9cb5bf84f9f5603d208b973a

Publish 2.3.8@e02afd2ad49708ea9cb5bf84f9f5603d208b973a #179

Triggered via push October 3, 2026 08:52
Status Success
Total duration 1m 7s
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
564 KB
sha256:34c6b650988840820d4a04e541cf0f0d604c18addec5d8f04c67fcac79a6545e
dist-handoff.tar
570 KB
sha256:c55efe3daedde5c52285332ccec4797b95fc920306099fef65d83c617cf4efe1