Skip to content

docs(security): pin v0.2.0 as the consumer-recommended release#465

Merged
zircote merged 1 commit into
mainfrom
docs/security-pin-v0.2.0
Jun 17, 2026
Merged

docs(security): pin v0.2.0 as the consumer-recommended release#465
zircote merged 1 commit into
mainfrom
docs/security-pin-v0.2.0

Conversation

@zircote

@zircote zircote commented Jun 17, 2026

Copy link
Copy Markdown
Owner

Summary

Pins v0.2.0 as the consumer-recommended release in SECURITY.md:

  • Supported Versions now names v0.2.0 (commit 67d8539d888070b1d00b9a59462c60dfad2f4fae) as the recommended pin, with a copy-paste uses: …@<sha> # v0.2.0 example and the SHA-pin-not-tag rule. Table updated (v0.2.0 recommended; < v0.2.0 best-effort).
  • New "Verifying this repo's own source release" subsection: the v0.2.0 bundle is signed by release.yml and carries three predicates (provenance, CycloneDX SBOM, vuln) — with the exact gh attestation verify loop pinning --signer-workflow to release.yml, and the signed-≠-passed caveat.

These commands are the same ones used to verify v0.2.0 from a workstation (all exit 0; 285-component SBOM, 0 vulns).

Type of Change

  • Documentation update

Test Plan

  • In-page anchor #verifying-this-repos-own-source-release resolves (slug check)
  • Pinned SHA matches the v0.2.0 tag commit
  • Verify commands match the working acceptance test for v0.2.0

Name v0.2.0 (commit 67d8539) as the recommended pin in Supported Versions,
and add a section to verify this repo own source release (the three
bundle-bound predicates: provenance, SBOM, vuln) signed by release.yml.
@zircote zircote merged commit 740cb8e into main Jun 17, 2026
7 checks passed
@zircote zircote deleted the docs/security-pin-v0.2.0 branch June 17, 2026 12:40
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.

1 participant