v2.4.0 — Version in the UI; popover dismisses on outside click

[2.4.0] - 2026-08-25

Added

• Version in the popover header — read from the running bundle rather than written as a
  literal, so what the UI claims and what is installed cannot disagree. A swiftc build with
  no bundle shows dev, which is the truthful answer there.

Fixed

• Popover stayed open when clicking another app — behavior = .transient was already set,
  but this is an LSUIElement agent that never becomes active, so a click belonging to a
  different application is never delivered to it and the popover simply hovered over whatever
  the user had moved on to. A global mouse-down monitor, installed while the popover is shown
  and removed in popoverDidClose, sees exactly the events .transient cannot. Clicks inside
  the popover are still .transient's job, which is why the monitor is global and not local.

v2.3.0 — Silent subtree loss fixed; Endpoint DLP guard

[2.3.0] - 2026-08-25

Added

• Endpoint DLP guard — on a Mac managed with Microsoft Purview, copying an unlabeled
  Office file to removable media is vetoed by the endpoint agent: copyfile() returns EPERM
  and macOS raises a modal justification dialog. During an unattended hourly backup nobody
  answers it and the file is never copied. DLPGuard now decides before the copy is attempted,
  so the dialog never appears. A file is skipped only when the destination is removable media,
  the file is an Office document, and it carries no MIP sensitivity label (read from
  docProps/custom.xml in the OOXML package).
• [dlp] config section — skip_unlabeled_office and skip_when_label_unknown, both
  defaulting to true. The TOML parser now understands booleans at all, which it previously did
  not.
• dlp_skipped report category — skipped files are counted in status.json
  (files_skipped) and named in errors.json, kept apart from real errors so a skip never
  inflates the error total. A file absent from the backup is always explainable.

Fixed

• Silent subtree loss in the scanner — FileScanner called enumerator.skipDescendants()
  for every entry matching an exclude pattern, files included. skipDescendants() skips the
  subdirectory the enumerator is about to descend into, so an excluded file sitting immediately
  before a real directory swallowed that entire subtree. Nothing failed and nothing was logged:
  the files were simply absent from every snapshot. A single stray .DS_Store was enough — on
  this machine it cost FDE_Update/zzArchive/ (6 files) and
  the-standing-egg/docs/archive/exports/ (4 files), and any *.log, *.tmp, *.pyc or
  *.jsonl in the wrong position would do the same. skipDescendants() is now called only for
  directories.
• Misleading advice on DLP failures — these surfaced as permission_denied, whose
  suggested action is "check Full Disk Access". No local setting fixes a Purview policy, so
  the operator was sent chasing a fix that does not exist.
• files_skipped never reported — the field was written to status.json but never
  assigned, so it always read 0 while errors.json listed skipped files.
• Stale recovery installer on the backup disk — install.sh synced the .app and then
  copied "the newest .pkg lying around", which nothing ever rebuilt. The artifact whose
  entire purpose is restoring the app from the backup had sat at 1.0.0 since March while the
  installed app moved on: the one scenario it exists for would have handed back a five-month-old
  build. install.sh now builds the installer it ships (build-pkg.sh, which produces the app
  once and both artifacts from it), pins the copy to the version it just built rather than to a
  glob, and removes any older .pkg from the disk so there are never two with no way to tell
  which matches the .app beside them. build-pkg.sh also derives the version from build.sh
  instead of repeating the literal — the same drift, one level down.
• Concurrency warnings in AppDelegate — four capture of 'self' with non-Sendable type
  warnings. AppDelegate touches AppKit and uiState throughout, both main-thread-only, so the
  isolation was already real and simply undeclared; the class is now @MainActor. runDiskutil
  is explicitly nonisolated, since handleEject calls it from a background queue precisely
  because it blocks. Builds clean.

Notes

• The DLP check runs after the hard-link attempt, not before. DLP vetoes the copy, not the
  link, so a file already present in the previous snapshot is still linked into the new one and
  stays in the backup chain. Enabling the guard never evicts what is already backed up.

v2.2.0

Release retroattiva: il tag v2.2.0 esisteva senza release, mentre l'artefatto era committato nel repo. Pubblicato qui per allineare tag e release e togliere i binari dal versionamento. Non è l'ultima versione — vedi Latest.

v2.1.0 — Fix restore, snapshot paths, custom backup, schedule UI

Cosa è cambiato

🔴 Fix critici

• Snapshot path (CRITICO) — i file erano salvati piatti nello snapshot (~/GitHub/MyRepo/file.swift → snapshot/file.swift). Ora vengono salvati con path relativo alla home (snapshot/GitHub/MyRepo/file.swift). Il restore su Mac diverso ora funziona.
• Restore su Mac nuovo — usava ConfigDiscovery.discover() che filtra solo i file già esistenti. Nuovo metodo candidatesForRestore() che matcha lo snapshot senza richiedere che i file esistano sul Mac di destinazione.
• Bug path ~/ — confirmRestore() non strippava il prefisso ~/ prima di passare i path a RestoreEngine (causava lookup su snapshot/~/.gitconfig che falliva sempre).
• Ordine restore — Homebrew installa i pacchetti prima di ripristinare i config file.

✨ Novità

• Aggiungi cartella al backup — pulsante ＋ Aggiungi cartella o file… nel tree di backup, apre Finder
• Destinazione restore personalizzata — pulsante ↗ su ogni item per scegliere dove ripristinarlo
• Schedule UI — menu Schedule nella popover (ogni ora, ogni 6h, notte) wired a launchd
• Restore progress — la popover si riapre durante il restore e mostra [X/N] filename
• Restore categories — il tree mostra Shell, Git, SSH, ecc. (non più Dotfiles/Folders)
• Tailscale aggiunto alla categoria Cloud

⚡ Performance

• Worker paralleli per il backup (8x TaskGroup, ~2x throughput)
• I/O throttle adattivo (AC vs batteria)

Installazione

• Prima installazione: RustyMacBackup-2.1.0-arm64.pkg (richiede admin)
• Aggiornamento: RustyMacBackup-2.1.0.app.zip (auto-update dalla popover)

v2.0.0

Release retroattiva: il tag v2.0.0 esisteva senza release, mentre l'artefatto era committato nel repo. Pubblicato qui per allineare tag e release e togliere i binari dal versionamento. Non è l'ultima versione — vedi Latest.

v0.3.1

Full Changelog: v0.3.0...v0.3.1

v0.3.0

Full Changelog: v0.2.0...v0.3.0

v0.2.0

Full Changelog: v0.1.0...v0.2.0

v0.1.0 — First Release

RustyMacBackup v0.1.0

First public release. A fast, incremental backup tool for macOS with a native menu bar app.

Highlights

• Backup engine — parallel file processing, hard links for unchanged files, 256KB buffered I/O
• Native menu bar app — Maranello Luce Design styling with Ferrari color palette
• Gradient progress bar — rosso → gold → verde with Core Graphics rendering
• Mini speedometer — Ferrari-style gauge showing real-time copy speed (MB/s)
• Disk-aware UI — detects disk connect/disconnect, disables actions when absent
• Error handling — categorizes errors (SIP/permissions shown as expected, not alarming)
• Smart scheduling — interval (15/30/60/120 min) or daily (2/3/4/6 AM)
• Battery guard — skips scheduled backups on battery power
• One-command install — bash install.sh handles everything

Install

git clone https://github.com/Roberdan/RustyMacBackup.git
cd RustyMacBackup
bash install.sh

Requirements

• macOS 13+ (Ventura)
• Full Disk Access for terminal + menu bar app