Repository navigation
build: Tag Cloud Build images with latest - #174
Merged
Merged
Conversation
Cloud Build pushes untagged child manifests, including BuildKit attestations, next to the tagged image. Picking an attestation in Cloud Run fails with "got 1 Manifest.Layers vs 0 ConfigFile.RootFS.DiffIDs". Add a cloudbuild.yaml that also tags the image with latest, and document deploying by tag. Co-Authored-By: Armen Zambrano Gasparnian <44410+armenzg@users.noreply.github.com>
armenzg
approved these changes
Nov 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deploying
gcr.io/sentry-dev-tooling/sentry-github-actions-app@sha256:0fabc1eb11…to Cloud Run failed with:Each build pushes three entries to GCR: the image index, which gets the commit SHA tag, plus two untagged child manifests, the platform image and a BuildKit attestation. An attestation has one in-toto "layer" and no root filesystem, which is what Cloud Run rejects. In the image picker, the untagged digests all look the same.
This adds a
cloudbuild.yamlthat tags the image withlatestas well as the commit SHA, so you can deploy:latestinstead of picking a digest.docs/deployment.mdnow says to deploy by tag. It doesn't change the attestations.Open decisions:
cloudbuild.yaml. Until then this file does nothing.--provenance=false --sbom=falseto the build. That removes supply-chain metadata, so this PR leaves it out.Not verified: I haven't run a Cloud Build with this config.
via @armenzg.
--
View Session [Sentry]