Tusk 0.4.2

Tusk v0.4.2 Release Notes

This release focuses on reliability and security ahead of the upcoming beta. You'll notice smoother handling of external drives during offloads, along with a range of under-the-hood protections that keep your credentials and footage safer.

---

🔒 Security & Safety

• Google OAuth tokens and S3 credentials are now stored and managed more securely, reducing exposure during project setup

• Sensitive file paths are no longer included in error reports sent for diagnostics

• App integrity verification (asar integrity) is now enabled, helping ensure Tusk hasn't been tampered with

• The log viewer now runs in a tighter sandbox with stricter content security policies, and developer tools are disabled in production builds

✨ Features

• Added end-to-end handling for drive disconnect and reconnect events during offload sessions

• New unit and integration tests cover file system safety and drive reconnection scenarios, improving confidence in edge-case behaviour

🐛 Fixes

• Fixed an issue where S3 credentials weren't being applied correctly when creating a new project

• When an external drive reconnects mid-offload, Tusk now clears any existing error messages and continues the offload automatically — no need to restart

• Fixed delete and restore operations to more reliably target the correct project folders

• Guarded against a rare crash that could occur when scanning unreadable folders during library reconciliation

🛠 Improvements

• File rename operations now go through a safer internal file system layer, reducing the risk of accidental data loss

• The offline grace period documentation has been updated to accurately reflect the 14-day limit

• Navigation and update-install actions now include additional safeguards against unintended triggers

---

> Offline grace period reminder: Tusk requires a connection to verify your licence every 14 days. Make sure to sync before heading off-grid for extended shoots.