Skip to content

v1.5.0

Choose a tag to compare

@SK360 SK360 released this 17 Nov 18:45
· 5 commits to main since this release

Backups, and installing no longer needs Python.

New

  • Backups. On each day your records change, a small ZIP of them (inventory, settings, filing log) is kept in
    out/backups/, the last 60 days. For a copy that survives the computer, Settings > Backups takes a folder on a
    USB drive or in a cloud folder: everything is copied there (records, settings, templates, approval PDFs, CLEO
    copies, your fingerprint/photo/trust files), then only what's new or changed, whenever the menu is open and the
    folder is there. The home screen warns if it hasn't been reachable for a week. Check my setup shows it too.
    The server pairing key is never copied. ./atf backup does it from the command line.

Changed

  • New installs don't need Python installed first. The installer downloads a pinned, checksum-verified copy of
    uv and uses it to put a private Python 3.13 in the folder's .uv folder (the .venv is made from it). Nothing is
    installed system-wide.
  • If uv can't be downloaded (offline, blocked, an unsupported computer), the installer says why and uses a Python
    3.9 to 3.14 already on the computer, as before. A checksum that doesn't match stops the install instead.
  • Existing installs: nothing to do. Re-running the installer keeps a .venv that already works, and updates from
    the menu behave as before (they never run the installer, and never touch .uv).
  • Delete .venv and .uv together to reinstall from scratch.
  • Tried live: a fresh install on a Windows PC (it got its own Python 3.13 although 3.11 was installed). Linux and the
    fallback only by the automated tests, which now install with no Python on Windows, Linux and macOS.
  • Backups: only by the automated tests so far.