Repository navigation
Release a patch release for 2024a tzdata #51933
Description
Activity
/cc @nodejs/releasers
It might be worth considering having a "simplified release process" for releasing timely sensitive patches as this one.
As far as I can tell, the code has already been updated to 2024a, however the last release is using 2023d. This is important because it includes a change to Kazakhstan's time zone, which starts on the 1 Mar 2024 (today!)
The release proposal for Node.js 21.7.0 includes this: #51932
#51723 updated the timezone for ICU 74. Node.js 20 and 18 are still on ICU 73.
@nodejs/lts Thoughts on whether we should separately patch the timezone database for ICU 73 for Node.js 20 and 18 or update with the commits on main (including updating to ICU 74.2)?
- added 10 commits that reference this issue
on Mar 18, 2024 FTR Node.js included the 2024a tzdata update in:
- 21.7.0
- 20.12.0
- 18.20.0
Reacted by Daniel Thomas and caryyu
What is the problem this feature will solve?
As far as I can tell, the code has already been updated to 2024a, however the last release is using 2023d. This is important because it includes a change to Kazakhstan's time zone, which starts on the 1 Mar 2024 (today!)
What is the feature you are proposing to solve the problem?
releasing a patch version, (afaik) no code changes required
To confirm the fix, one can run
process.versions.tzin a node consoleWhat alternatives have you considered?
No response