bcp v0.2.11

Fixed: Windows updates now actually work

On Windows, the desktop app could keep showing the previous version after reporting an update succeeded, and then claim the app was "already latest" on the next check. This happened because the shell serves the app over http://tauri.localhost, so the PWA service worker registered inside the embedded webview and its cache kept serving the old build.

This release:

• Skips the service worker in the desktop shell so the webview can only render the freshly installed bundle.
• Sweeps the webview profile once per release on first launch: clears cached origin data, unregisters any stale workers, and reloads, so already-affected machines self-heal on this update.
• Shows the running binary version in the sidebar and About screen instead of the bundled string, so the displayed version always matches what the updater compares.

macOS and Linux never had this issue (the shell there uses a non-HTTP scheme) but also pick up the binary-version display and the same one-time safety sweep.

More reliable releases

The release pipeline now verifies itself before shipping:

• Version sync check - package.json, Cargo.toml, tauri.conf.json, and the UI version constant must agree.
• Service worker guard check - the desktop shell stays out of the PWA worker on all platforms.
• Release artifact validation - latest.json, every per-platform installer and its signature, and the rootless Linux tarball are checked against the tag before the release goes out.

Checksums

All installers ship with minisign signatures (.sig files) alongside their latest.json entries.

Note: the updates you see in-app (Linux rootless, and this fix) are part of ongoing automation; the Tauri updater validates signatures before installing.