Publish 2.0.0-rc.38@76bc2c15f70d6c4a814815fcf13d9aefd01ab6b2 from direct #154
publish.yml
on: push
build
29s
publish-test
0s
deploy-and-audit-api-reference
2m 58s
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
|
574 KB |
sha256:55131ec3d7d69e9e2419854b00517d71f86a854c9e4922cea6d7bf76ed0c2d77
|
|
|
dist-handoff.tar
|
580 KB |
sha256:c7f0617b70a98378bdde7d072ad8af98979424adab57381e7d1926e656922e95
|
|