Skip to content

fix: don't create an artifact storage record for the image attestation - #4

Merged
rubenhensen merged 1 commit into
mainfrom
rhensen/yiv-401-no-storage-record
Oct 22, 2026
Merged

rubenhensen merged 1 commit into
mainfrom
rhensen/yiv-401-no-storage-record

Conversation

@rubenhensen

Copy link
Copy Markdown
Contributor

actions/attest-build-provenance creates an artifact storage record by default when it pushes to a registry. That needs artifact-metadata: write, which none of the callers grant, so every Delivery run ended with "Failed to create storage record". We don't use storage records, so docker-publish.yml now sets create-storage-record: false. The provenance attestation itself is unchanged.

The alternative was asking every caller for artifact-metadata: write. With callers on the moving @v1 tag, that would have broken every caller that doesn't grant it.

CHANGELOG: v1.1.2.

Part of YIV-401.

The attest action creates a storage record by default, which needs
artifact-metadata: write from every caller. We don't use storage records,
so every run ended with a warning. The attestation itself is unchanged.
@rubenhensen
rubenhensen merged commit 9c10ee4 into main Oct 22, 2026
2 checks passed
@rubenhensen
rubenhensen deleted the rhensen/yiv-401-no-storage-record branch October 22, 2026 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant