v2.10.1
Pre-launch hardening. Everything here came out of a review done before promoting the project, while it still had essentially no users.
Auto-update was silently broken for non-ASCII account names
If your Windows account name isn't plain ASCII — C:\Users\홍길동\…, and likewise for Japanese or Chinese names — auto-update did nothing and took the app with it. The update downloaded, its SHA-256 verified, you clicked "restart to update", the app exited… and never came back. No error, no installer.
The helper batch was written as UTF-8, but cmd.exe reads batch files in the OEM code page, so the installer path inside it came out as mojibake and the batch failed to execute a single line. It's now written in the code page cmd actually reads, and if a path can't be encoded at all, Notro launches the installer directly instead.
Reproduced on a Hangul path and verified end to end after the fix.
If you're on 2.10.0 or earlier and your account name has non-English characters, the in-app update will not work. Download
NotroSetup.exebelow and run it once — from then on updates work normally.
Also
NotroSetup.exenow carries version information instead of showing a blank properties dialog.- Builds no longer depend on what's installed on the machine doing the build.
--collect-all webviewhad been collecting numpy and cryptography from a development machine — 37 MB the app never imports. Published installers were never affected (CI installs only the declared requirements), but a locally built release would have been.
New documentation
- SECURITY.md — what Notro reads and stores, the complete list of the four network endpoints it contacts, where every file lives, and how to verify an unsigned download. Short version: nothing you copy is ever transmitted, there is no telemetry, and clipboard images are only saved if you turn that on.
- THIRD-PARTY-NOTICES.md — bundled components and their licenses.
- CODE_SIGNING.md — how releases are built and what will govern signing.
NotroSetup.exe.sha256 below.
Full Changelog: v2.10.0...v2.10.1