Repository navigation
docs: document SmartScreen first-launch warning - #242
Merged
Merged
Conversation
The released `csshw.exe` is not code-signed, so Windows SmartScreen shows a "Windows protected your PC" warning on first launch. Until the binary is signed, document the warning and the bypass options (More info -> Run anyway, Properties -> Unblock, or `Unblock-File`) so users hitting it know what to do. Add the note to both the README and the release template so it appears on the GitHub release page next to the download link, which is where most users first encounter the issue. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
whme
added
the
no-news-fragment-needed
|
🤖 News Fragment Check ✅ Success! This PR meets the news fragment requirements. |
The reviewer asked for two clarifications in the release template: the SmartScreen warning is unavoidable because the per-binary code- signing certificate costs money, and the release `.zip` itself is signed with a GitHub build attestation starting with 0.19.0. Document both: clarify why `csshw.exe` is unsigned, and add a "Verifying the download" section explaining how `gh attestation verify` proves that the archive came from this repository's release workflow at the tagged commit. Mirror the addition in the README so both entry points agree. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
whme
commented
May 23, 2026
whme
commented
May 23, 2026
Drop the "code-signing certificate costs money" aside from the SmartScreen note in both the README and the release template - the fact that the exe is unsigned is what users need to know; the funding rationale is not. In the release template, move the "Verifying the download" section below the download button so the download call-to-action is reached before the attestation details. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Documents the expected Windows SmartScreen first-launch warning for the unsigned csshw.exe, and provides users with clear bypass options until code signing is available. Also adds download provenance verification guidance so release notes include attestation instructions alongside the download link.
Changes:
- Added a SmartScreen first-run warning note (and bypass steps) to the README.
- Added the same SmartScreen note to the release template so it shows up on GitHub Releases.
- Added “Verifying the download” instructions (GitHub build attestation /
gh attestation verify) to the release template.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| templates/release_template.md | Adds SmartScreen warning + GitHub attestation verification instructions to release notes template. |
| README.md | Adds SmartScreen warning note (plus reference to release-note verification instructions). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The released
csshw.exeis not code-signed, so Windows SmartScreenshows a "Windows protected your PC" warning on first launch. Until
the binary is signed, document the warning and the bypass options
(More info -> Run anyway, Properties -> Unblock, or
Unblock-File) so users hitting it know what to do.Add the note to both the README and the release template so it
appears on the GitHub release page next to the download link, which
is where most users first encounter the issue.
Co-authored-by: Claude Opus 4.7 noreply@anthropic.com