Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#1,185 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
internationalization, release

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
JavaScript
Stelle
4.4k
Fork
678
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nodejs/Release

Tutte le issue di nodejs/Release

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.