github mauriceboe/TREK v3.0.1
v3.0.1 — Reservations hotfix

latest releases: v3.0.3, v3.0.2
6 hours ago

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.

Don't miss a new TREK release

NewReleases is sending notifications on new releases.