Skip to content

Codex Lifeboat v3.4.5

Latest

Choose a tag to compare

@github-actions github-actions released this 16 Sep 06:22
304b0ec

Codex Lifeboat 3.4.5 — Windows backup robustness

Nederlands

Codex Lifeboat 3.4.5 resolves the Windows backup failures reported in issue #5.

Fixed

  • Shortened internal staging-directory names to reduce the Windows path-length budget.
  • Added an early destination path-budget check with exact 259, 260, and 261-character boundary coverage.
  • Added clear diagnostics when Windows long-path support or the selected destination cannot safely contain required backup data.
  • The destination folder is now always selectable, including when exactly one removable USB drive is connected.
  • Copy failures for reconstructable .pyc, .pyo, and __pycache__ files are recorded as warnings instead of aborting an otherwise valid backup.
  • Required files and core Codex data remain fail-closed.
  • Duplicate rollouts are resolved when the database path and expected collection identify one canonical file.
  • Non-canonical duplicate rollouts, including divergent copies, are preserved as hashed, non-restorable evidence without modifying the source profile.
  • Rollout reports now contain the exact thread IDs, source paths, package paths, sizes, timestamps, and hashes needed for diagnosis.
  • Failed staging directories receive an INCOMPLETE.json marker and can never be mistaken for a completed backup.
  • Added bounded retries for brief Windows antivirus or indexer locks during atomic metadata replacement.

Validation

  • All 84 source checks pass.
  • All 84 checks pass from the packaged Windows executable.
  • All 12 automated Windows compatibility scenarios pass.
  • The standalone executable includes Tcl/Tk and passed its packaged self-test.
  • SHA-256 checksums are included with the release.

Download

Download Codex-Lifeboat-Windows-x64-Portable.zip, extract it completely, and run Codex-Lifeboat.exe.

The executable remains unsigned. Physical testing with the reporter's exact profile and USB device is still recommended as final real-world confirmation.