Skip to content

Publish 2.0.0-beta.21@cf64edae927b3fd139c5b60ec18ee5bfff826314 from direct #128

Publish 2.0.0-beta.21@cf64edae927b3fd139c5b60ec18ee5bfff826314 from direct

Publish 2.0.0-beta.21@cf64edae927b3fd139c5b60ec18ee5bfff826314 from direct #128

Triggered via push July 27, 2026 14:36
Status Success
Total duration 1m 0s
Artifacts 3

publish.yml

on: push
publish-test
publish-test
verify-docs-release-audit
6s
verify-docs-release-audit
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
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.
Docs release-audit tuple stale
https://durable-workflow.com/docs-page-release-audit.json reports artifact_versions.sdk-python=2.0.0-beta.18, expected 2.0.0-beta.21. Run npm run refresh:public-artifact-versions in durable-workflow.github.io and land scripts/public-artifact-versions.json plus docs/compatibility.md through the normal docs merge path before treating this release as fully surfaced. When DOCS_RELEASE_AUDIT_HANDOFF is set, the uploaded handoff artifact contains the pipeline-ready docs refresh request.

Artifacts

Produced during runtime
Name Size Digest
dist
427 KB
sha256:1799c6df80ded5e0bdabb1bd2714f6fa2ba0ea71dab86e434920039b129d370c
dist-handoff.tar
440 KB
sha256:976505d2d66d35d6d2027937afd6595b783fc89faabef724bbcc2d18393fe25a
docs-release-audit-evidence
2.67 KB
sha256:bc0c9b1f5fe838ef66852a22ea5c43b2658e0a6919cba5b7911f4fb8580bad1a