Skip to content

docs: pin signer workflow and tag on the runbook's attestation verify - #63

Merged
VirtualMachinist merged 2 commits into
mainfrom
docs/runbook-attestation-pins
Oct 31, 2026
Merged

VirtualMachinist merged 2 commits into
mainfrom
docs/runbook-attestation-pins

Conversation

@VirtualMachinist

@VirtualMachinist VirtualMachinist commented Oct 31, 2026 •

Copy link
Copy Markdown
Member

Follow-up to #62. Docs only: docs/custody-upgrade-runbook.md and docs/install.md.

Both files ran gh attestation verify <archive> --repo Hedronite/facet. --repo alone accepts an attestation from any workflow in the repo, built from any ref. Both now:

  • pin --signer-workflow Hedronite/facet/.github/workflows/release.yml, --source-ref refs/tags/v<version> and --source-digest <tag commit> (the tag commit comes from gh api);
  • verify SHA256SUMS with the same pins, not only the archive;
  • check the archive with shasum -a 256 -c SHA256SUMS --ignore-missing (install.md also gives the Linux sha256sum -c form).

The runbook's step 1 now points to a new "Verify the release" block. The install guide's "Release archive provenance" block is replaced in place and keeps the literal 0.8.0 used by the rest of that page.

Checked against v0.8.0

I ran both blocks as written on the published assets:

  • the pinned verify exits 0 on facet-cli-0.8.0-macos-arm64.tar.gz, facet-cli-0.8.0-linux-x64.tar.gz and SHA256SUMS;
  • shasum -c prints OK for both archives;
  • the same verify with --source-ref refs/tags/v0.7.9 exits 1, so the pin rejects a wrong ref.

No code, test, workflow or dependency changes.

🤖 Generated with Claude Code

VirtualMachinist and others added 2 commits October 31, 2026 09:21
Step 1 of the root-custody upgrade runbook ran `gh attestation verify`
with `--repo` only, which accepts an attestation from any workflow in
the repo, built from any ref. Pin `--signer-workflow` to release.yml,
`--source-ref` to the version tag and `--source-digest` to the tag's
commit, verify SHA256SUMS the same way, and check the archive with
`shasum -c`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The install guide's provenance check ran `gh attestation verify` with
`--repo` only. Use the same pins as the custody runbook
(`--signer-workflow` release.yml, `--source-ref` the v0.8.0 tag,
`--source-digest` its commit), verify SHA256SUMS too, and check the
archive with `shasum -c` (`sha256sum -c` on Linux).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@VirtualMachinist
VirtualMachinist marked this pull request as ready for review October 31, 2026 15:06
@VirtualMachinist
VirtualMachinist merged commit c38d2bc into main Oct 31, 2026
12 checks passed
This was referenced Nov 13, 2026
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