BLOG-36 Fix workflow buildx failed to push #37

Closed
squid wants to merge 2 commits from BLOG-36_fix_buildx_failed_to_push into main
Owner

Description

  • As the title

Package Changes

No response

Screenshots

No response

Reference

Checklist

  • A milestone is set
  • The related issuse has been linked to this branch
### Description - As the title ### Package Changes _No response_ ### Screenshots _No response_ ### Reference - Resolves #36 - Solution: https://stackoverflow.com/questions/75131872/error-failed-to-solve-failed-commit-on-ref-unexpected-status-400-bad-reques - Docker document: https://docs.docker.com/build/ci/github-actions/attestations/#max-level-provenance > Note that adding attestations to an image means you must push the image to a registry directly, as opposed to loading the image to the local image store of the runner. This is because the local image store doesn't support loading images with attestations. ### Checklist - [x] A milestone is set - [x] The related issuse has been linked to this branch
squid added this to the Phase I milestone 2025-01-28 03:31:48 +08:00
zoe was assigned by squid 2025-01-28 03:31:48 +08:00
squid added 2 commits 2025-01-28 03:31:48 +08:00
BLOG-36 fix: let buildx push without provenance
All checks were successful
Frontend CI / build (push) Successful in 1m52s
PR Title Check / pr-title-check (pull_request) Successful in 12s
3943137b75
squid changed title from BLOG-36_fix_buildx_failed_to_push to BLOG-36 Fix workflow buildx failed to push 2025-01-28 03:32:32 +08:00
squid closed this pull request 2025-01-28 04:16:13 +08:00
All checks were successful
Frontend CI / build (push) Successful in 1m52s
Required
Details
PR Title Check / pr-title-check (pull_request) Successful in 12s
Required
Details

Pull request closed

Sign in to join this conversation.
No description provided.