v3.3.2

Homelable 3.3.2

Completes the 3.2.0 -> 3.3.x upgrade. If your devices came back blank after updating — no ip, no services, no hostname, no hardware — this is the release that brings them back. Nothing was lost: the facts stayed in the database the whole time, the migration just never carried them across.

3.3.1 stopped the upgrade from breaking saves and approvals, but the migration itself still aborted, on timestamps SQLite hands back as text. It aborted on the first node that had ever been reached by a status check, which is why so few installs escaped it.

Affected installs repair themselves on the next start. Nothing to do by hand. If any device is still blank afterwards, the backend log now names that node and the reason, which is worth pasting into an issue.

Full changelog

Fixes

• Devices upgraded from 3.2.0 keep their ip, services, hostname, notes and hardware. The migration no longer aborts on last_seen / last_scan, and a node that cannot be migrated for any reason now costs only itself instead of the whole canvas. (#347, #348 — thanks @mhwlng, @rlko and @hqzw6hoaR for the reports and the logs)
• A canvas saved while an earlier migration was stuck no longer loses its device facts. That save linked the node to a blank inventory row; the migration now fills it in rather than skipping the node and dropping the columns that held its only copy. (#347)