If provenance not specified but Buildx version compatible for attestation, disable provenance anyway. While the action successfully pushes OCI compliant images to well-known registries, some runtimes (e.g. Google Cloud Run and AWS Lambda) are not able to pull resulting image from their own registry.
When merged we are going to create a v3.3.1 patch release. In follow-up we will create a v4.0.0 release that keeps provenance enabled, just like v3.3.0.
related to https://github.com/docker/buildx/issues/1533
fixes #780 fixes #778 fixes #771
If
provenancenot specified but Buildx version compatible for attestation, disable provenance anyway. While the action successfully pushes OCI compliant images to well-known registries, some runtimes (e.g. Google Cloud Run and AWS Lambda) are not able to pull resulting image from their own registry.When merged we are going to create a v3.3.1 patch release. In follow-up we will create a v4.0.0 release that keeps provenance enabled, just like v3.3.0.