CHANGELOG

System Evolution & Stability Logs

Release / 2026-04-04

WINDOWS 1.0.13: UPDATER DELIVERY AND DOWNLOAD LINKS REPAIRED

Windows updater delivery is restored in 1.0.13, the public manifest now serves a valid inline signature, and website downloads now point at current release files.

What changed: - Windows updater manifest now serves inline minisign payload instead of a .sig URL. - Older Windows builds can resolve the 1.0.13 update again without the parser failure seen in the broken manifest. - Public website downloads were re-aligned with the actually published release files. - Licensing delivery and release helper paths were hardened so the same manifest-shape bug is less likely to return. Release status: - windows/x86_64 updater to 1.0.13: live. - Public /api/dl/windows: points to the 1.0.13 setup executable. - Public /api/dl/macos: points to the current published macOS archive.

→Updater API now returns inline signature payload, not a URL reference.
→The 1.0.13 Windows setup download is live from whisperone.app and updates.whisperone.app.
→The macOS external download route now targets the current published archive instead of an old 1.0.9 artifact.
→Release registration tooling now resolves signature input from URL, file path, or inline content before writing the manifest.
→License delivery and website download fixes were verified against the live production endpoints.

ACTION: Open WhisperOne and retry the in-app update, or download the current installer from the Download page.

Release / 2026-04-01

WINDOWS PORTABLE ZIP ADDED, PLUS A FIRST-RECORDING HOTKEY FIX

WhisperOne now has a Windows portable ZIP for environments where the normal installer cannot be used.

What changed: - Added a Windows portable ZIP build that can be extracted and run without the normal installer. - Trial and normal license activation both work in the portable build. - Portable Full includes a bundled Small model, so onboarding can complete without a separate model download. - Fixed a Windows first-cycle push-to-talk bug where the first recording after startup could remain active until extra input was received. Release status: - Windows portable Full ZIP: published. - Windows portable Lite ZIP: published. - Regular Windows installer/updater rollout for these additional portable-validation fixes remains a separate follow-up publish.

→Full portable ZIP: https://updates.whisperone.app/artifacts/1.0.12/windows/x86_64/WhisperOne-Portable-Full-Small-1.0.12.zip
→Lite portable ZIP: https://updates.whisperone.app/artifacts/1.0.12/windows/x86_64/WhisperOne-Portable-Lite-1.0.12.zip
→Portable package now has one obvious entrypoint: WhisperOne.exe.
→Portable validation smoke covered onboarding, bundled model detection, trial, license activation, restart persistence, and the first push-to-talk recording after cold start.

ACTION: Download the Windows portable build

Release / 2026-03-12

WHISPERONE 1.0.12: WINDOWS PUBLISHED, MACOS PENDING

Windows users received the 1.0.12 wave with the bundled payload.

What changed: - Windows users received the 1.0.12 wave with the bundled payload. - Included hotkey/start latency stabilization. - Included the Windows No Mic tooltip visibility fix. Technical details: - The release split covered 2026-03-10 through 2026-03-12. - 1.0.11 had already shipped to users on both targets. - The hotkey/start latency stabilization and Windows parity package remained local-only until this wave. - The version contract was raised to 1.0.12. Release status: - windows/x86_64 for 1.0.12: published. - darwin/aarch64 for 1.0.12: pending (requires build/publish from the macOS host).

→Release split covered 2026-03-10 through 2026-03-12.
→1.0.11 had already shipped to users on both targets.
→The hotkey/start latency stabilization and Windows parity package remained local-only until this wave.
→The version contract was raised to 1.0.12.

ACTION: Update to version 1.0.12

Release / 2026-03-10

MACOS: FEWER UNNECESSARY KEYCHAIN PROMPTS DURING REFRESH

The indicator should no longer get stuck because of a false InstallToApplications state in non-bundle runtime.

What changed: - The indicator should no longer get stuck because of a false InstallToApplications state in non-bundle runtime. - A manual forced refresh in an active online context no longer performs an unnecessary secure rewrite when the bundle is already valid. - The secure-operation budget in tests is now lower and more predictable. Technical details: - Root cause was confirmed from runtime logs. - Missing permissions: InstallToApplications was being raised even when Accessibility and Microphone permissions were already granted. - Cause: health_check could not recover the bundle path and marked the installation as unstable. - A guard was added in apps/desktop/src/platform/macos/permissions.rs. Release status: - Publication status requires manual verification.

→Root cause was confirmed from runtime logs.
→Missing permissions: InstallToApplications was being raised even when Accessibility and Microphone permissions were already granted.
→Cause: health_check could not recover the bundle path and marked the installation as unstable.
→A guard was added in apps/desktop/src/platform/macos/permissions.rs so non-bundle dev/release executable paths no longer add InstallToApplications.
→The secure online-refresh path now uses a lower prompt budget.

ACTION: Open the full changelog

Release / 2026-03-11

POST-RELEASE SAFETY REFACTOR CLOSED (WAVE 7–8)

We closed the post-release master plan by extracting safer seams from a core hotspot and finishing the closeout work so future fixes are lower-risk.

Shipping isn’t just features—it’s making the next hotfix safer than the last one. On March 10, 2026, Wave 7 focused on behavior-neutral refactor: helper modules were extracted out of coordinator.rs, and a runtime unwrap() in online-license evaluation was replaced with a safe conversion. Windows automation gates were run to keep this work honest. On March 11, 2026, Wave 8 closeout finished the master plan: completed plans were moved into docs/plans/done, memory docs were updated, and the outcome was captured as risk reduction around large hotspots—plus clearer seams for the next wave. It’s still rough around the edges, but this is the kind of work that prevents “one tiny fix” from turning into a fragile cascade.

→Wave 7: helper module extraction from coordinator.rs
→Runtime unwrap() removed from online-license evaluation path
→Windows automation gates run after extraction
→Wave 8: master-plan closeout completed and documented
→Finished plans moved to docs/plans/done; memory docs updated
→Outcome: reduced risk around core hotspots; prepared seams for next wave

ACTION: If you rely on WhisperOne daily, this is the boring work that keeps fixes fast and controlled.

Release / 2026-03-09

MACOS HOTFIX CHAIN: UPDATER IDENTITY, VISIBILITY, AND FEWER KEYCHAIN PROMPTS

A focused macOS hotfix chain stabilized updater identity, improved update visibility, and reduced surprise Keychain prompts—culminating in 1.0.10 shipped via updater.

macOS needed a hardening pass where “it updated” wasn’t enough—the update had to stay stable after it landed. The chain started with 1.0.4, which fixed the updater-only signing path so artifacts keep a stable identity (identifier "com.whispone.app") and continuity from 1.0.3 -> 1.0.4 was published and endpoint-smoked. Update visibility was then tightened (including native notifications and a backend-owned tray state), and by 1.0.9 the overall UX was stable: continuity passes, notifications arrive, permission UI/tray behaves, restarts don’t spam Keychain, and License refresh is explicit-only. On March 9, 2026, 1.0.10 was published via the production updater (1.0.9 -> 1.0.10) with endpoints confirmed. It’s still rough around the edges, but the “update loop” is now calmer and more predictable.

→1.0.4: stable updater identity restored (com.whispone.app), continuity verified
→1.0.6: native notifications fixed + backend-owned tray state + refresh loop, continuity verified
→1.0.9: License tab avoids Keychain unless you explicitly refresh
→Startup policy defers secure-touch for active online state; regression test added
→1.0.10 published via updater on 2026-03-09; 200/204 endpoint smoke confirmed

ACTION: If you’re on macOS, open WhisperOne and update to 1.0.10 via the in-app updater.

Release / 2026-03-07

WINDOWS HARDENING: TRANSCRIPT POST-PROCESSING + UPDATE NOTIFICATIONS THAT PERSIST

Windows hotfix work added an optional transcript post-processing guardrail and made update discovery harder to miss by persisting update state and sending OS notifications.

On March 7, 2026, we tightened two Windows pain points: output sanity and update visibility. First, we brought a downstream transcript guardrail into the main runtime via a new TextPostProcessor, plus settings (text_post_processing_enabled and text_post_processing_method). Post-processing happens before history/clipboard/final emit—so the guardrail sits where it actually matters. Second, the updater flow was hardened so “an update exists” becomes durable: the backend keeps the found update in process-level state, sends both an in-app toast and a native OS notification, and the UI state moved into SettingsContext so it doesn’t disappear when Settings closes. On March 6, 2026, we also hardened privacy in the license gateway by normalizing device_id server-side to a sha256 format (without double-hashing already-hashed values), backed by tests. It’s still rough around the edges, but the system is harder to surprise and easier to trust.

→New Windows TextPostProcessor + settings; runs before emit to history/clipboard
→Update discovery stored in backend state (not a transient UI toggle)
→Dual-channel update signal: in-app toast + native OS notification
→Updater UI state moved into SettingsContext for persistence
→License gateway: server-side device_id normalization to sha256, with tests
→Windows verification parity fix: line-ending agnostic UI contract assertion (\n vs \r\n)

ACTION: Open Settings to enable post-processing and keep an eye on the improved update prompts.

Release / 2026-03-05

WHISPERONE 1.0.0 FINALIZED (UPDATER LIVE ON WINDOWS + MACOS)

WhisperOne 1.0.0 is finalized, with the in-app updater live on both platforms and the delivery contract verified end-to-end.

On March 5, 2026, WhisperOne 1.0.0 moved from “almost there” to closed and verifiable: the updater is live for Windows and macOS, and the delivery contract was checked across both targets. On macOS, the publish path included uploading the signed updater artifacts (WhisperOne.app.tar.gz + .sig) plus a WhisperOne_1.0.0_aarch64.dmg, and activating the updater manifest row. It’s still rough around the edges in places, but the release pipeline is now grounded in checks we can trust.

→1.0.0 finalized with updater live on Windows + macOS
→macOS publish: signed tarball + DMG uploaded; manifest row activated
→Contract verified: 0.99.93 -> 200, 1.0.0 -> 204 (Windows + macOS)
→VirusTotal handoff prepared: Windows EXE, macOS DMG, SHA256SUMS.txt

ACTION: Open WhisperOne and use the in-app updater to get 1.0.0.

09 / Resources

NAVIGATE

Download

Latest Version

Explore

Legal

Product

For Mac
For Windows
Docs

Specification

Native Rust Core
GPU Accelerated
On-Device AI
Apple Silicon/Intel
Windows

Contact

Support Email

Built for: Apple Silicon/Intel & Windows. Hardware Accelerated. Private Speech-to-Text.