Identify the commit serving on a Cloud Run revision
Read Serving revision on the deployment page to distinguish the commit verified through an image digest from other declarations about the build.
Check what bound the revision to its commit#
For a deploy to Cloud Run, Serving revision, or Serving revisions when it lists more than one, follows Pull requests instead. It lists each revision the newest check of this deploy found serving traffic, with its share of traffic when it serves less than all of it. Commit is the commit the revision served. Bound by says how Proofline tied the revision to that commit:
| Bound by | Meaning |
|---|---|
| Attestation of the image digest | A GitHub attestation of the revision's image digest, made by the deploy's repository, names the commit. |
| Revision label only | No attestation binds the image. The revision's commit-sha label names the commit, and anyone who can deploy the service can set that label. |
| Not bound | Neither an attestation nor a label names a commit. |
| Not recorded | The check ran before Proofline recorded how revisions were bound. |
Under Revision label only and Not bound, the page says why no attestation bound the revision: its containers pin no single image digest, Proofline could not read provenance for the digest, GitHub holds no attestation of the digest, every attestation of the digest was refused, or the attestations name more than one commit. A refusal names what each refused attestation failed, such as a signature that does not verify. When GitHub holds no attestation of the digest, or only refused ones, an administrator also sees Publish build provenance. The attestation step it describes works the same for an image Cloud Run serves: attest the digest the build pushes.
When the revision's commit-sha label names another commit than the attestation, Revision label names it. The attested commit is the one the check compares.