This is a maintenance release that fixes an upgrade problem reported after 2.2.0. If your instance is already running 2.2.0 normally, there is nothing to change beyond the upgrade.
Fixes
- Upgrade to 2.2.0 could stop at the database migration (#657). A manual transport-type correction recorded on a trip with zero length was carried over as an empty time range, which the new timeline-edit table does not allow. The migration rolled back on every restart, so the backend kept restarting and the UI showed a 502 Bad Gateway error.
- The upgrade now repairs these corrections before migrating them. Where the trip still exists, its duration is taken from the trip; corrections that can no longer be applied are skipped instead of blocking the upgrade. The same cleanup also covers corrections that 2.2.0 already migrated.
- Corrections saved with an unknown transport type or a blank visit label no longer interrupt timeline rebuilding.