Repository navigation
docs: add SignPath application prerequisites - #15
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ed58346d03
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Every stable Windows release must use a trusted Authenticode code-signing | ||
| identity and an RFC 3161-compatible trusted timestamp. An unsigned prerelease | ||
| candidate may be published only for testing or signing-provider evaluation, | ||
| must carry a prominent unsigned warning, and must not be promoted to a stable |
There was a problem hiding this comment.
When an unsigned candidate is published for testing under this new exception, the repository gives maintainers conflicting release requirements: this policy permits it, while README.md:93-96 still says all public releases require trusted, timestamped signatures. Clarify there that the signature requirement applies to stable/final releases and explicitly preserve the unsigned-prerelease exception so the documented publication gate is unambiguous.
Useful? React with 👍 / 👎.
Summary
Verification