Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nodejs does not recognize the changes to Africa/Cairo timezone changes #47818

Closed
abumostafa opened this issue May 2, 2023 · 3 comments
Closed
Labels
v18.x Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.

Comments

@abumostafa
Copy link

Version

18.6.0

Platform

Linux 86892fc3d811 5.15.49-linuxkit #1 SMP Tue Sep 13 07:51:46 UTC 2022 x86_64 Linux

Subsystem

No response

What steps will reproduce the bug?

On 28th of April, there was a decision to use the DST in Egypt. However, Nodejs did not recognize the change

https://www.timeanddate.com/time/change/egypt

Nodejs time

Welcome to Node.js v18.16.0.
Type ".help" for more information.
> new Date().toLocaleString('en-US', { timeZone: "Africa/Cairo" })
# '5/2/2023, 1:34:31 PM'
>

Machine time

TZ=Africa/Cairo date
# Tue May  2 14:35:06 EEST 2023

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

there must be an update to the date library to recognize the recent changes

What do you see instead?

time without DST

Additional information

No response

@mscdex
Copy link
Contributor

mscdex commented May 2, 2023

The change is in version 2023a of the timezone database, which has yet to land in v18.x. However, v20.x includes 2023c if using v20.x is an option for you.

@tniessen tniessen added the v18.x Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch. label May 2, 2023
@abumostafa
Copy link
Author

abumostafa commented May 2, 2023

The change is in version 2023a of the timezone database, which has yet to land in v18.x. However, v20.x includes 2023c if using v20.x is an option for you.

Thanks @mscdex. an upgrade was possible.

@bnoordhuis
Copy link
Member

Good to hear. I'll close this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v18.x Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.
Projects
None yet
Development

No branches or pull requests

4 participants