Skip to content

Publish 2.0.0-beta.6@695b6fc65c7d0227bafa2b4fa92bd2043a76368c from direct #121

Publish 2.0.0-beta.6@695b6fc65c7d0227bafa2b4fa92bd2043a76368c from direct

Publish 2.0.0-beta.6@695b6fc65c7d0227bafa2b4fa92bd2043a76368c from direct #121

Triggered via push July 23, 2026 04:56
Status Success
Total duration 1m 5s
Artifacts 3

publish.yml

on: push
publish-test
0s
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.5, expected 2.0.0-beta.6. 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:e130fb148506e30739220c299898cf7c0960fac0aff85fc5e7029719c4d7b563
dist-handoff.tar
440 KB
sha256:1f278876419143a19555a4297812fd61c6bc5ad2db150bceb01627853a12204a
docs-release-audit-evidence
2.65 KB
sha256:558ac6470ca2d9a8cf22204c19c8e32a24f2415456317502d22ee0ea7fde9814