You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# gh attestation verify pihole-FTL-amd64 --owner pi-hole
Verifying attestations for the artifact found at file://pihole-FTL-amd64
Failed to verify the artifact: failed to fetch attestations for subject: sha256:67e7d2451a29ff3cd21c4a7c489ac4b1d43993f4a69bf9fbe989dda47f24685e
# gh attestation verify pihole-FTL-amd64 --repo pi-hole/FTL
Verifying attestations for the artifact found at file://pihole-FTL-amd64
Failed to verify the artifact: failed to fetch attestations for subject: sha256:67e7d2451a29ff3cd21c4a7c489ac4b1d43993f4a69bf9fbe989dda47f24685e
gh attestation verify pihole-FTL-amd64 --owner pi-hole --bundle ./pi-hole-FTL-attestation-793098.sigstore.json
Verifying attestations for the artifact found at file://pihole-FTL-amd64
Failed to verify the artifact: failed to fetch attestations for subject: sha256:67e7d2451a29ff3cd21c4a7c489ac4b1d43993f4a69bf9fbe989dda47f24685e
Describe the bug
We just added attestation building to our workflow to join the beta.
Steps to reproduce the behavior
gh attestation verify pihole-FTL-amd64
is expected to work, but we getExpected vs actual behavior
Expect attestation to be validated. The
sha256sum
of the built and downloaded binaries match:Logs
Files for reproduction
The text was updated successfully, but these errors were encountered: