Wishing Planner

Version 1.4.1 for Windows

Windows may show "Windows protected your PC" because the installer is not code-signed: More info, then Run anyway. Installed copies update themselves from Settings > Updates.

What's new

Small release about how versions are released. Calculations, saved data, schema, workspace files and dependencies are unchanged.
- Fix: "Install a newer version…" in Settings > Updates now looks like a button (outlined, like Check for updates). It was drawn as plain text.
- Publish guard. npm run all and npm run release read the version that is online before building and uploading. If the version in the source is the same or older, nothing is built or uploaded: the run ends with RESULT: NOT published and a Windows notification says why. An unreachable site only warns and the run continues. --force publishes anyway, for example to replace a bad upload.
- First in-app update. Installed 1.4.0 copies receive this version through Settings > Updates (header button, Windows notification, Install and restart). It is signed with the same key as 1.4.0.
- Cargo.lock is now part of the project: the first Windows build of 1.4.0 generated it. Copy it into each new source folder so builds use identical Rust dependencies; the source archive includes it. The 1.4.0 note that it remains absent no longer applies. npm run all prints a note when it is missing.
- Documentation: new docs/release-process.md (the steps of every release); README, SETUP_GUIDE and docs/setup-cloudflare.md describe the guard and Cargo.lock; TEST_RESULTS.md holds the real results of the 1.4.0 Windows run.
- Tests: tests/unit/release141.test.ts.