Repository navigation
Backplane 0.14.1 hotfix
Fixes #907: the Windows app could remain on Connecting to service unless started as administrator or with Windows Developer Mode enabled. First-run log setup now uses a hardlink instead of a privileged file symlink. Startup failures show the actual error and offer Retry instead of retrying silently forever.
This hotfix is based on the 0.14.0 release commit 94532cfb, with only the Windows repair, its CI coverage and required 0.14.1 version metadata. Release source: e564f904eb277ffbd8d0104d6d8afa90ff1aeb6f.
Downloads
| Platform | Download |
|---|---|
| Windows x64 | Portable ZIP |
| Linux x64 | tar.gz |
| Linux ARM64 | tar.gz |
| macOS Apple Silicon | tar.gz |
| Web | Web client archive |
| Android | Signed APK · AAB |
| iOS | Signed IPA · Xcode archive |
The versioned installer and latest installer both select v0.14.1 and verify the desktop archive checksum. Additional AppImage, DEB and classic updater formats are not included in this initial hotfix download set.
Known issues
- The hub's memory grows over hours of use; restart Backplane if it gets slow.
- The first start after an update can take up to a minute.
These previously disclosed Alpha issues remain open; this hotfix does not claim to fix them.
Opening desktop downloads
Windows: Extract the portable ZIP and open Backplane normally. Administrator rights and Developer Mode are not required. The portable build remains unsigned; if SmartScreen blocks it, choose More info → Run anyway, where offered. Managed-device policy may prevent this override.
macOS: The build has an ad-hoc seal, without Apple Developer ID signing or notarization. If blocked, try opening it, then use System Settings → Privacy & Security → Open Anyway. Use the override only for the Backplane download you chose.
Qualification and provenance
The packaged Windows app was checked with an actual standard-user token, Developer Mode disabled, and a denied-symlink negative control. It started its own service from an empty home, connected and reached the main UI; the startup-failure UI was checked too.
Unchanged web/mobile code, helpers and native runtime components reuse their 0.14.0 evidence. Version-bumped Android, iOS and web packages do not claim a new emulator or end-to-end campaign. Checksums and per-component build/reuse provenance are attached as SHA256SUMS and RELEASE-PROVENANCE.json.