Upgraded from 2.2.x to 2.3.4, 2.3.5, 2.3.6 or 2.3.7? Read this
That upgrade silently emptied every backup plan's repositories and hook scripts, and detached past runs from their plans (#860). Scheduled backups then failed with Backup plan has no enabled repositories, visible only in the server log.
2.3.8 fixes the cause and repairs affected installs on first start, reading the lost rows back from the rollback database the upgrade kept next to the live one (borg_bak.db). Plans you already re-linked by hand are left as you set them. Check your plans once after updating.
Upgrades from 2.3.0 to 2.3.3, and fresh installs, were never affected.
What's Changed
- chore(release): bump version to 2.3.8 (0151aec)
- fix(db): run SQLite migrations with foreign keys off so batch rebuilds do not cascade (#1303) (eeec389)
- ci: run checks and CodeRabbit on PRs into borg2-b25 (#1302) (a3eb40c)
- chore(deps-dev): bump brace-expansion from 5.0.7 to 5.0.12 in /frontend (#1286) (73ebe5e)
- ci(deps): bump actions/setup-python from 6 to 7 (#1301) (3a402cc)
- fix: let backups queue behind a prune dry run instead of refusing them (#1299) (16ed2b6)
- chore(deps): bump undici and wrangler in /updates-worker (#1287) (15dfbf7)
- test(smoke): wait out run follow-ups before the next plan run (#1298) (30b8aef)
- chore(coderabbit): inherit UI settings instead of replacing them (b2ed690)
Docker Images
Published to Docker Hub:
docker pull ainullcode/borg-ui:2.3.8
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.3.8/install.sh
curl -fsSL https://github.com/karanhudia/borg-ui/releases/download/v2.3.8/install.sh.sha256 | sha256sum -c - \
&& sudo bash install.sh --version 2.3.8
Full Changelog: v2.3.7...v2.3.8