Request: v24.x (and v22.x) patch release with tzdata 2026e before 2026-10-31 (Manitoba permanent UTC-5)
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 18/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
調査の方向性
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 の本文から書いたものです。
説明
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 theCanada/Centrallink) 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 dov24.x-stagingandv22.x-stagingtoday.
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 onmainon 2026-10-02. It carrieslts-watch-v24.xandlts-watch-v22.x. - It only touches
deps/icu-small/source/data/in/icudt78l.dat.bz2andtest/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-stagingandv22.x-stagingare all on ICU 78.3 with the sameicudt78ldata file name, so no ICU version change is needed on either LTS line. Agit cherry-pickwill 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
- A minimal v24.x patch release (e.g. 24.22.1) with #66419 landed, shortly after 2026-10-21 and before 2026-10-31.
- The same for v22.x, if feasible.
- 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
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
nodejs/Release のほかの issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
-
Release-agenda
難易度 1/5 1〜3時間 初心者へのやさしさ 78/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 5/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 20/100
-
Node.js Release WorkGroup Meeting 2026-08-20対応中かも @sxa が 53 日前に担当しました。 オープン
難易度 1/5 1時間未満 初心者へのやさしさ 35/100
似ている issue
-
Add: EUROTV NEWSオープンchannels:add check:passed
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
-
curriculum documentation quality
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
githubnext/gh-aw-workshop#4638 ·
メンテナーはふだん 1 日以内に返信
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
openclaw/openclaw-enterprise#2571 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
fabriziosalmi/certmate#1247 ·
メンテナーはふだん 1 日以内に返信
-
[guide] docs/metrics/index.md names retired 'Import reference architectures' workflow as the metrics refresh path対応中かも @hivecommons-hive が今日担当しました。 オープンagent/guide documentation hive/covered-by-pr hive/hosted-available-lke648397-260827-5n31
難易度 1/5 1時間未満 初心者へのやさしさ 70/100
cncf/endusers#1537 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信