Skip to content

DRAFT-HOLD: v0.3.0 'Verify a release yourself' (every v0.3.0 command TO-VERIFY). Do not merge before the first tag released through the new chain - #41

Closed
fosterstack-admin wants to merge 1 commit into
mainfrom
www/verify-a-release-v030-hold
Closed

fosterstack-admin wants to merge 1 commit into
mainfrom
www/verify-a-release-v030-hold

Conversation

@fosterstack-admin

Copy link
Copy Markdown
Contributor

Advisor request (Oct 9), item 2. Written from matrix rev 2 [GUIDE] ACs 24-28, 47-49 and dossier section 2c wording ('signed at every stage, verified together at release'). It is an OUTLINE: the v0.3.0 chain is unverified (observer-tool test not run), so every command and v0.3.0-only claim is marked TO-VERIFY, the trust-boundaries section is TO-FILL, and no SLSA level is claimed. noindex while held. It deliberately collides with #40 on the same path (/verify-a-release/): at launch this version replaces the v0.2.1 page. Open question for the advisor in the page's HTML comment: AC47 bans tool names in the guide yet the guide must run cosign/gh/jq by name; v0.2.1 page does.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying www with  Cloudflare Pages  Cloudflare Pages

Latest commit: 31e04ad
Status: ✅  Deploy successful!
Preview URL: https://f1fecb71.www-4rw.pages.dev
Branch Preview URL: https://www-verify-a-release-v030-ho.www-4rw.pages.dev

View logs

@fosterstack-admin

Copy link
Copy Markdown
Contributor Author

Superseded by #165 and now by the preview (#172): the v0.3.0 verify-a-release page lives there with confirmed file names and signing identities.

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