Skip to content

Normalize inbound API dates to the application timezone - #437

Open
ashwinuae wants to merge 2 commits into
cachethq:mainfrom
ashwinuae:api-date-timezone-normalise
Open

Normalize inbound API dates to the application timezone#437
ashwinuae wants to merge 2 commits into
cachethq:mainfrom
ashwinuae:api-date-timezone-normalise

Conversation

@ashwinuae

Copy link
Copy Markdown
Contributor

Timestamps submitted to the API for either schedules or incidents, with an explicit ISO-8601 UTC offset (e.g. 2026-08-06T18:31:37Z) had their offset discarded at write time (as 2026-08-06 18:31:37).

FlexibleDateTimeCast now converts every value to the application timezone, so the wall clock that reaches the database always represents the correct instant.

Timestamps without offsets are still parsed per application-timezone wall clock (as before), so existing clients are unaffected. Existing rows written under the bug are left as-is since they are indistinguishable from correct values.

Closes #434

ashwinuae and others added 2 commits August 20, 2026 23:42
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

API timestamps with explicit UTC offset are silently shifted when APP_TIMEZONE is not UTC

1 participant