Skip to content

fix: use TokenUtility for persistent bond lookup after terminate #68

fix: use TokenUtility for persistent bond lookup after terminate

fix: use TokenUtility for persistent bond lookup after terminate #68

Triggered via push January 21, 2026 23:01
Status Failure
Total duration 1m 58s
Artifacts 1

release.yml

on: push
Quality & Security
1m 35s
Quality & Security
Build & Release
16s
Build & Release
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Quality & Security
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0P1txaQAAAADTt5Gds1vjS5sPc81UzM9XUEFPRURHRTA2MTQARWRnZQ==
Quality & Security
Failed to restore: Cache service responded with 400
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 & Release
Failed to restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
gitleaks-results.sarif Expired
6.59 KB
sha256:727dbf56bd86f06b1b84b4e0e2d04d5ec3a0c981ed3a3f5669749f1d48da661f