Skip to content

ci: disable provenance attestations on image pushes — ACR rejects them - #425

Merged
fengttt merged 1 commit into
mainfrom
fix-acr-provenance
Aug 14, 2026
Merged

ci: disable provenance attestations on image pushes — ACR rejects them#425
fengttt merged 1 commit into
mainfrom
fix-acr-provenance

Conversation

@fengttt

@fengttt fengttt commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

The nightly "Build and Push Images" runs have been failing on both architectures (e.g. runs 31749181599 from the 2026-08-13 cron — predating #418 — and yesterday's dispatch 31826694057) with:

denied: unknown manifest class for application/vnd.oci.empty.v1+json

on the ACR push. Aliyun ACR rejects the OCI attestation manifests that buildx now attaches by default. This sets provenance: false / sbom: false on both push steps — the product image build and the new ci-builder job (which pushes to the same ACR mirror and would fail identically on its first real publish).

🤖 Generated with Claude Code

Every nightly product-image push to registry.cn-shanghai.aliyuncs.com
has been failing with

  denied: unknown manifest class for application/vnd.oci.empty.v1+json

(runs 31749181599, 31826694057 and earlier): Aliyun ACR rejects the OCI
attestation manifests buildx attaches by default. Set provenance: false
and sbom: false on both push steps (product image and ci-builder) so
pushes emit plain image manifests both registries accept.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@fengttt
fengttt merged commit 2fea540 into main Aug 14, 2026
1 check passed
@fengttt
fengttt deleted the fix-acr-provenance branch August 14, 2026 18:14
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