Open MatthewHaas19 opened 1 year ago
I can confirm this issue. This is maybe related that Mexico shifted time for last time.
Is there a plan to fix this bug?
I have the same problem, any news about the fix?
We had to update our node version to 14.21.2. Also, make sure the browser you're using is up-to-date
On Tue, Sep 26, 2023 at 10:51 AM Pablo Viñuales @.***> wrote:
I have the same problem, any news about the fix?
— Reply to this email directly, view it on GitHub https://github.com/iamkun/dayjs/issues/2302#issuecomment-1735704054, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQFIWWJSX42YR6ZBX3ODLNTX4LTWDANCNFSM6AAAAAAXTANIWE . You are receiving this because you commented.Message ID: @.***>
Thank you, but it doesn't look like it will be of any use to us. We are already using Node version 16.3 and our application uses Electron which is where the problem seems to be (old Chromium version). Upgrading the Electron version does not work either because we would lose users on Windows 7 and 8.
Describe the bug In the past Mexico_city timezone was changing in april (from GMT-6 to GMT-5). But now the timezone is always GMT-6 in Mexico. And right now with dayjs.tz we are still in CDT(GMT-5) and it's incorrect.
Expected behavior Set America/Mexico_city to GMT-6 (always)
Information