v0.6.7 - Historical Traceroute Positions

What's New

Historical Traceroute Positions

Traceroutes now store node positions at the time they were completed. The map renders routes to where nodes actually were, not where they've moved to since. MeshMonitor sources use the new routePositions API field; MQTT sources snapshot last-known positions from the database at ingestion time. When historical positions aren't available, the frontend falls back to current node positions.

Bug Fixes

• Fixed anonymous user migration failing due to missing totp_enabled column in INSERT
• Added server_default declarations for all NOT NULL columns with Python defaults, preventing raw SQL INSERT failures on older installs

Pull Requests

• #93 - feat: Support route_positions in traceroutes
• #92 - fix: Add server_default declarations and migration for NOT NULL columns
• #91 - fix: Include totp_enabled in anonymous user migration INSERT
• #94 - chore: Bump version to 0.6.7

Full Changelog: v0.6.6...v0.6.7