Release v2.6.19
This commit is contained in:
@@ -2,6 +2,40 @@
|
||||
|
||||
All notable changes to this project will be documented in this file.
|
||||
|
||||
## 2.6.19 - 2026-08-09
|
||||
|
||||
### Changed
|
||||
|
||||
- Timetable editor helpers, routes, and table layout now use timetable-specific naming and tighter card/table styling.
|
||||
- Connected clients now sort by client identity fields instead of the old IP-based ordering assumption.
|
||||
|
||||
## 2.6.18 - 2026-08-09
|
||||
|
||||
### Changed
|
||||
|
||||
- Timetable tables were renamed from the old `schedule` names to `timetable` names, and existing databases now rename those tables during migration.
|
||||
- The timetable group editor now uses timetable-specific naming in its shared helpers and keeps the entries table aligned with the standard admin card/table layout.
|
||||
|
||||
## 2.6.17 - 2026-08-09
|
||||
|
||||
### Changed
|
||||
|
||||
- Existing timetable groups and entries are now migrated to Europe/London, and timetable dates are rewritten to UTC using that source timezone so the wall-clock meaning stays intact.
|
||||
|
||||
### Fixed
|
||||
|
||||
- New timetable groups now default to Europe/London so the timetable editor and saved data start from the same timezone assumption as the migrated rows.
|
||||
|
||||
## 2.6.16 - 2026-08-09
|
||||
|
||||
### Changed
|
||||
|
||||
- Timetable groups now store an IANA time zone and render their entry datetimes in that timetable time zone, so schedules keep the same wall-clock meaning when they are edited from another country.
|
||||
|
||||
### Fixed
|
||||
|
||||
- Timetable entry date inputs now round-trip through the timetable time zone instead of the browser locale, so saving from Florida while targeting Germany keeps the intended local times.
|
||||
|
||||
## 2.6.15 - 2026-08-08
|
||||
|
||||
### Fixed
|
||||
|
||||
Reference in New Issue
Block a user