Skip to content

TREK

v3.0.1 Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 1mo Productivity & Wikis
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

budget-tracker collaborative opensource packing-list poi real-time
+11 more
routes self-hosted travel travel-app travel-planner traveling trip trip-planner wanderlog wanderlust webapplication

Affected surfaces

breaking_upgrade

Summary

AI summary

Fixed non-transport bookings being incorrectly placed on day 1 regardless of reservation time.

Full changelog

Fixes a v3.0.0 regression where non-transport bookings (tours, restaurants, events, other) landed on day 1 of the trip regardless of their actual reservation_time.

Fix (#832)

  • Migration 122 — for every non-hotel reservation, nulls out any day_id / end_day_id that doesn't match the reservation's time, then backfills from reservation_time / reservation_end_time. Runs automatically on startup, is idempotent, and leaves already-correct rows alone.
  • reservationServicecreateReservation / updateReservation now derive day_id / end_day_id from the reservation time when the client doesn't send one explicitly, so the mismatch can't come back on new or edited bookings.

Upgrade

docker compose pull && docker compose up -d

No manual steps required — migration 122 runs on startup.

Note

Bookings whose reservation_time lies outside the trip's date range (e.g. entered with the wrong month) will end up with day_id = NULL and temporarily drop out of the day plan. Open each of those and correct the date to bring them back.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track TREK

Get notified when new releases ship.

Sign up free

About TREK

Real-time collaborative travel planner

All releases →

Related context

Related tools

Beta — feedback welcome: [email protected]