Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Request: v24.x (and v22.x) patch release with tzdata 2026e before 2026-10-31 (Manitoba permanent UTC-5)

未关闭
  • 哪里不对？
#1,185 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
18/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
领域
internationalization, release

调研方向

This is a release-planning request, not a code change, and the decision belongs to the Release WG. The payload points to deps/icu-small/source/data/in/icudt78l.dat.bz2 and test/fixtures/tz-version.txt, which #66419 updates to tzdata 2026e, and to the v24.x and v22.x staging branches. A newcomer could check whether the staging branches' tz-version fixture matches the stated tz 2026c, but the work is done when a maintainer schedules and ships the patch release.

由索引模型根据 Issue 内容生成。

描述

Release-agenda

Hi Release WG,

As @richardlau suggested in https://github.com/nodejs/node/pull/66667#issuecomment-6166334035, I'm opening this as a separate issue so it can be discussed at a Release WG meeting. Could a maintainer please add the Release-agenda label? I can't add it myself.

I know releasers are volunteers and that a release before 2026-10-31 depends on someone having time. I'm asking whether it's feasible, and I'm offering to do whatever prep work helps.

What changes and when
  • tzdata 2026e (2026-09-29) puts Manitoba (America/Winnipeg, and the Canada/Central link) on permanent UTC-5 from 2026-10-31. In the data, this means the 2026-11-01 02:00 fall-back no longer happens.
  • tzdata 2026d (NWT, effective 2026-11-01) is also missing from the LTS lines.
  • v24.22.0 and v22.23.3 both ship tz 2026c (test/fixtures/tz-version.txt), as do v24.x-staging and v22.x-staging today.

From 2026-11-01, any Intl.DateTimeFormat or Date timezone conversion for those zones on a current LTS release will be one hour off. Users on platforms that can only run upstream Node.js builds can't fix this until a release ships. Managed runtimes such as AWS Lambda's nodejs22.x / nodejs24.x are one example.

The change itself
  • https://github.com/nodejs/node/pull/66419 (deps: update timezone to 2026e) landed on main on 2026-10-02. It carries lts-watch-v24.x and lts-watch-v22.x.
  • It only touches deps/icu-small/source/data/in/icudt78l.dat.bz2 and test/fixtures/tz-version.txt. Its data file already includes 2026d, so it alone also covers https://github.com/nodejs/node/pull/66333.
  • It shipped in 26.11.0 on 2026-10-07, so it reaches the usual two weeks in a Current release around 2026-10-21.
  • main, v24.x-staging and v22.x-staging are all on ICU 78.3 with the same icudt78l data file name, so no ICU version change is needed on either LTS line. A git cherry-pick will report conflicts, because the staging branches are on 2026c and #66419 was made against 2026d. Both conflicts are resolved by taking the incoming file.
The ask
  1. A minimal v24.x patch release (e.g. 24.22.1) with #66419 landed, shortly after 2026-10-21 and before 2026-10-31.
  2. The same for v22.x, if feasible.
  3. If neither fits, a stated plan for when 2026e will reach each line, so downstream users can plan around it.

I'm aware the v24.x release plan has the Maintenance transition on 2026-10-20. This request doesn't depend on whether the release is labelled Active or Maintenance.

Workaround and precedent

As noted in https://github.com/nodejs/node/pull/66667#issuecomment-6166380488, ICU's drop-in .res override (ICU_TIMEZONE_FILES_DIR, see https://github.com/nodejs/Release/issues/773#issuecomment-1229046695) works. However, every deployment has to ship and maintain the data files and configure the environment, so it isn't a practical fix for most users.

Similar time-critical tz updates were raised before in https://github.com/nodejs/Release/issues/576 (Morocco, 2020a) and https://github.com/nodejs/Release/issues/773 (Chile, 2022b). The general ICU-in-release-line policy discussion is in https://github.com/nodejs/Release/issues/679.

Thanks for considering this, and for all the work that goes into the release lines.

主要语言
JavaScript
星标
4.4k
派生
678
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

nodejs/Release 的其他 Issue

查看 nodejs/Release 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。