Skip to content

docs: clarify <tag> in attestation verify command (UID2-6764)#2540

Merged
BehnamMozafari merged 1 commit into
mainfrom
bmz-UID2-6764-clarify-tag-readme
May 13, 2026
Merged

docs: clarify <tag> in attestation verify command (UID2-6764)#2540
BehnamMozafari merged 1 commit into
mainfrom
bmz-UID2-6764-clarify-tag-readme

Conversation

@BehnamMozafari
Copy link
Copy Markdown
Contributor

Summary

  • Clarifies that <tag> in the gh attestation verify command is the Docker image tag (bare semantic version, no v prefix — e.g. 5.70.84), not the git/release tag (v5.70.84).
  • Adds a "Where to find a tag" list pointing at GitHub Packages, the release-name shortcut, and digest pinning for exact-manifest verification.
  • Collapses the example command onto a single line so it copy-pastes cleanly on Windows shells as well as macOS/Linux (no \ line-continuation).

Follow-up to UID2-6764 (artifact signing and provenance rollout) — wording-only.

Test plan

  • Render README.md on GitHub and confirm the section reads cleanly.
  • Confirm the example command, copy-pasted as-is, runs against a real tag substituted in.

🤖 Generated with Claude Code

Explain that <tag> is the Docker image tag (no v prefix) and document
where to find it. Also collapse the example command onto one line so it
copy-pastes on Windows and macOS shells.

UID2-6764

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@BehnamMozafari BehnamMozafari merged commit 439fa82 into main May 13, 2026
9 checks passed
@BehnamMozafari BehnamMozafari deleted the bmz-UID2-6764-clarify-tag-readme branch May 13, 2026 03:04
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.

2 participants