We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v14.21.3
No response
v14.21.3 release includes out-of-date tzdata2022f
The ICU repository was just updated to include the binary files 2 months ago: https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew/2023c/44
It includes an update to Egypt DST that already took effect April 28th.
The text was updated successfully, but these errors were encountered:
node@14 already End-of-Life on 2023-04-30. You should use node@18 or node@20 instead.
node@14
2023-04-30
node@18
node@20
Sorry, something went wrong.
v18 has the same problem it's not updated but v20.1.0 is up todate
Welcome to Node.js v18.16.0. Type ".help" for more information.
new Date().toString() 'Sat May 06 2023 10:46:43 GMT+0200 (Eastern European Standard Time)'
Welcome to Node.js v20.1.0. Type ".help" for more information.
new Date().toString() 'Sat May 06 2023 11:48:38 GMT+0300 (Eastern European Summer Time)'
See discussion in #47872. Closing.
No branches or pull requests
Version
v14.21.3
Platform
No response
Subsystem
No response
What steps will reproduce the bug?
v14.21.3 release includes out-of-date tzdata2022f
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
The ICU repository was just updated to include the binary files 2 months ago:
https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew/2023c/44
It includes an update to Egypt DST that already took effect April 28th.
Additional information
No response
The text was updated successfully, but these errors were encountered: