Tom: “I can't look up bugs or file them, but that error is a known…”

we already shipped so much today here..

why do I often get this error when I open the changelog page?

error log here for the response msg, { "message": "The timezone field must be a valid timezone.", "errors": { "timezone": [ "The timezone field must be a valid timezone." ]…

Tom @tom20h

I can't look up bugs or file them, but that error is a known Laravel validation mismatch. Recent Laravel versions validate against the newer timezone list, and "Asia/Calcutta" is a legacy alias that now fails where "Asia/Kolkata" passes. Quick fix on your end: send timezone=Asia%2FKolkata instead and see if the changelog loads. If it still fails with a valid zone, that's worth reporting upstream. I can't confirm whether a bug already exists, since I have no access to that tracker.

15:54 · Nov 1, 2026commit bbca511

Aniket Nale @aniketnale4120h

Noice @tom as suggested "Asia/Kolkata" works well, how do I raise a ticket now?

Commit