v3.0.0

3.0.0 (2026-02-08)

⚠ BREAKING CHANGES

• The REST API changes and will break clients.
• app: API endpoints now require and return date-time strings with timezone offsets.
• service: Service interfaces now use OffsetDateTime. getNextDepartures is renamed to getStopTimes. getNearestStops signature is modified.
• raptor: RaptorAlgorithm interface now uses OffsetDateTime instead of LocalDateTime.
• gtfs: Public interface of the GtfsSchedule and model classes now require OffsetDateTime instead of LocalDateTime. GtfsSchedule has replaced getNextDepartures with getStopTimes.
• app: API Error response schema change.

Features

• app: migrate REST API to OffsetDateTime (eb80037), closes #422
• app: standardize api level errors and separate validation logic in controller (936befd), closes #174
• gtfs: migrate to OffsetDateTime and implement DST-safe stop time requests (eb46bf6), closes #422
• gtfs: update link to timetable 2026 for switzerland (e74a69c)
• move validation handling to service package in app (b32ccd4)
• raptor: apply UTC offsets in route scanning and post-processing (2c6ada5), closes #422
• raptor: migrate RAPTOR router to OffsetDateTime for timezone-awareness (42e8226), closes #422
• raptor: return local agency timezones instead of UTC (88480c4), closes #422
• service: migrate to OffsetDateTime and update APIs (c7af86f), closes #422
• service: sort connection and isoline query results (0f5d38a), closes #422

Bug Fixes

• correct distributionUrl in maven-wrapper.properties (dba9711)
• correct distributionUrl in maven-wrapper.properties (c7ac8f1)
• docker: resolve build failure from deprecated base image (581b8b7)

Code Refactoring

• standardize terminology for durations and transfers (261e208), closes #422