GitBack v0.5.4
A reliability-focused update with safer runtime behavior, stronger diagnostics, and better protection against unexpected failures.
🛠️ What's Fixed
Sync no longer silently succeeds with zero assets.
If a repository or gist list couldn't be read (permissions issue, corrupted file), GitBack used to log a quiet warning and report a successful sync of zero repos. It now fails loudly instead, so a real problem can't be mistaken for "nothing to back up."
gitback init is safer.
Existing configurations, tokens, or sync data are no longer overwritten accidentally. Re-running initialization requires explicit --force when an existing setup is detected.
gitback discovery now respects the global lock.
GitBack operations are serialized consistently, preventing discovery from running alongside sync or snapshot operations.
Shutdown is handled cleanly.
Ctrl+C and systemctl stop now trigger graceful shutdown, release the lock, and avoid abrupt termination during active work.
Git failures now include useful diagnostics.
Clone and update failures now preserve Git's actual error output in the logs instead of producing empty or misleading error entries.
doctor and health reports now provide a complete picture.
Previously, one failed check (like a missing config) could stop the rest of the diagnostics from running. Both commands now check everything they can and show all of it at once. Making operational problems easier to identify in one run.
Additional reliability fixes.
- Fixed a rare case where GitBack's git credentials could be read inconsistently by git subprocesses.
- Fixed a file handle leak when another GitBack process is already running.
🔄 Upgrade
No configuration or storage layout changes are required.
Update the GitBack binary and continue using your existing installation.