Borg UI 2.4.6 focuses on backup and restore reliability, actionable diagnostics, and safer failure handling. Updating is recommended.
Highlights
- Safer backups: backups fail visibly when configured SSH sources cannot be prepared, instead of silently leaving those sources out. Already-mounted sources are cleaned up after preparation failures.
- More trustworthy restores: zero-file restores with supported Borg warning codes are marked failed. Local, SSHFS and managed-agent restore failures retain useful, bounded diagnostics. Restore checks stage their canary on remote-direct hosts correctly.
- Better recovery guidance: repository, prune, mount and API errors retain actionable causes. Storage-full and I/O failures produce clearer guidance; repeatedly failing background archive syncs back off, and lock contention is retried.
- Source setup fixes: generated source scripts are reused, and database discovery explains scan failures.
- Security hardening: stronger credential redaction in persisted diagnostics, escaped restore notification HTML, dependency updates, and source maps excluded from native install tarballs.
- Interface improvements: clicking locked controls opens the relevant upgrade card; eligible users can claim a one-time 5% offer inside a card they opened. Front-truncated paths retain their left-to-right order. Announcement validation and version targeting are more robust.
- Engineering: faster PR CI with scope-aware checks and test sharding, plus expanded regression coverage and troubleshooting documentation.
Upgrade note
Borg 2 backups now consistently require a plan that includes Borg 2 across scheduled, manual and retry entry points. After full access or an eligible licence expires, affected schedules pause visibly and report the plan requirement. Review this before upgrading installations that relied on the previous enforcement gap.
The managed-agent version remains 0.1.22; this release contains no agent-package changes.
What's Changed
- chore(release): bump version to 2.4.6 (707faa2)
- fix(sources): reuse generated source scripts; database scans say why they failed (#1500) (ddda536)
- fix: fail zero-file restores and retain actionable diagnostics (#1506) (574a273)
- fix: validate announcements and missing app versions (#1503) (0248019)
- fix: fail backups when source preparation is incomplete (#1502) (2811f72)
- fix(ui): keep front-truncated paths in left-to-right order (#1497) (f37014e)
- fix: preserve actionable repository, prune and mount errors (#1505) (67df006)
- feat(plan): one-time 5% offer in the upgrade cards the user opened (#1495) (8f3f179)
- Speed up PR CI while preserving required checks (#1508) (4cc344b)
- fix: write foreground mount stderr to a temporary file (#1507) (a9ad2a1)
- fix: surface storage failures and pace failing archive syncs (#1504) (f64f0ee)
- chore(deps): bump undici and wrangler in /updates-worker (#1501) (01bfd90)
- fix(licensing): stop Borg 2 backups when the plan no longer includes Borg 2 (#1499) (ab9cdf1)
- docs(readme): plans and pricing section (#1494) (9db0d42)
- feat(plan): locked controls answer the click with the upgrade card (#1493) (1c1ca2b)
- fix(remote): stage restore-check canary on remote-direct hosts (#1490) (#1492) (1a5aa58)
- fix(release): ship no source maps in the native install tarball (#1489) (a9db0c7)
- fix: make API request failures actionable (#1488) (499fc7f)
- fix(operations): retry server archive sync lock contention (#1487) (10e13c9)
Docker Images
Published to Docker Hub:
docker pull ainullcode/borg-ui:2.4.6
docker pull ainullcode/borg-ui:latest
Install without Docker
Debian or Ubuntu host (bare metal, VM, or LXC):
curl -fsSLO https://github.com/karanhudia/borg-ui/releases/download/v2.4.6/install.sh
curl -fsSL https://github.com/karanhudia/borg-ui/releases/download/v2.4.6/install.sh.sha256 | sha256sum -c - \
&& sudo bash install.sh --version 2.4.6
Full Changelog: v2.4.5...v2.4.6