Skip to content

docs: the code signing policy in the download step and in each release's notes - #68

Merged
httpsphl merged 2 commits into
mainfrom
docs/code-signing-policy-link
Sep 30, 2026
Merged

httpsphl merged 2 commits into
mainfrom
docs/code-signing-policy-link

Conversation

@httpsphl

Copy link
Copy Markdown
Owner

What

SignPath Foundation's terms ask for the term "Code signing policy" on the project's home page and on its download/release pages. Botloft applied on 2026-09-30.

  • README: the download step links the code signing policy. Before, the link was only inside the collapsed "Why does Windows warn me" question.
  • Release notes: release.mjs ends the "Verify your download" section with a link to the policy, so every release page from the next one has it.
  • Policy: the Status section says Botloft applied to the SignPath Foundation, and that the page will say so if the application is accepted. The attribution sentence SignPath asks for ("Free code signing provided by SignPath.io, certificate by SignPath Foundation") comes only after approval, since until then it would not be true.
  • Spec 15.5 notes the link in the release notes.

Tests

Text only, plus one line in the notes template. pnpm check passes on the merge of this branch with every open PR and main.

…e's notes

SignPath Foundation asks for the term "Code signing policy" on the project's home and download pages. The README linked it only inside a collapsed question; now the download step does, and every release's notes end with it. The policy says Botloft applied to the SignPath Foundation on 2026-09-30.
@httpsphl
httpsphl enabled auto-merge September 30, 2026 17:23
@httpsphl
httpsphl merged commit e90a686 into main Sep 30, 2026
3 checks passed
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