[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
tzdata	==2026.3 → ==2026.5

---

Release Notes

python/tzdata (tzdata)

v2026.5: : Release of upstream tzdata 2026e

Compare Source

Version 2026.5

Upstream version 2026e released 2026-09-30T00:14:38+00:00.

Briefly:

Manitoba moves to permanent -05 on 2026-10-31.

Changes to future timestamps

Manitoba’s 2026-03-08 spring forward was its last foreseeable clock change, as
it moved to permanent -05 thereafter. Model this with its traditional
abbreviation EST. Although the change to permanent -05 legally takes place on
2026-10-31, temporarily model the change to occur on 2026-11-01 at 02:00 for the
same reason as other recent temporary hacks. (Caution: see “NOTE FOR 2026b
TEMPORARY HACK FOR CLDR AND CANADA” below.)

As the change affects both America/Winnipeg and its backward compatibility link,
the obsolescent setting TZ="Canada/Central" will now use the abbreviation EST
for affected timestamps, akin to TZ="Canada/Pacific" behavior introduced in
2026b.

Another TZDB release may be needed soon if any of the portions of northwestern
Ontario historically aligned with America/Winnipeg do not follow. For now,
given the short leadtime with Manitoba’s announcement, assume that they will, to
avoid creating new zones that may not be needed if no divergence occurs.

Changes to past timestamps

In 1925 Ireland fell back on 09-20 not 10-04 (thanks to Stan Ulbrych).

Changes to commentary

Discussion on timekeeping practices in northwestern Ontario has been expanded in
light of Manitoba’s recent announcement. It is not yet known whether or to what
extent these areas may adapt their own timekeeping practices in response.

v2026.4: : Release of upstream tzdata 2026d

Compare Source

Version 2026.4

Upstream version 2026d released 2026-09-11T22:21:07+00:00

Briefly:

Canada’s Northwest Territories moved to permanent -06 on 2026-08-21. Obsolescent
settings like TZ="EST5EDT" now conform better to POSIX. Fix security,
performance and porting bugs in zic and localtime.

Changes to future timestamps

Canada’s Northwest Territories will not fall back on 2026-11-01 and will stay on
-06 year-round, matching Alberta’s recent change. Model this with its
traditional abbreviation CST. Although the change to permanent -06 legally took
place on 2026-08-21, temporarily model the change to occur on 2026-11-01 at
02:00 for the same reason as other recent temporary hacks. (Caution: see “NOTE
FOR 2026b TEMPORARY HACK FOR CLDR AND CANADA” below.) This affects only
America/Inuvik as the rest of the territory is covered by America/Edmonton, for
which the equivalent change was released in 2026c.

Changes to past timestamps

Colombia’s 1992-05-02 spring forward was at 00:00, not 24:00.

Iran’s 1979-05-26 spring forward was at 00:00, not 24:00. (Thanks to N.F. Hase.)

The backward-compatibility names EST5EDT, CST6CDT, MST7MDT, and PST8PDT now
conform better to POSIX. For example, EST5EDT now always uses the abbreviation
"EST" for standard time (now always 5 hours behind UT) and "EDT" for daylight
saving time, whereas it formerly had different UT offsets before standard time
was introduced and sometimes used abbreviations like "LMT", "EWT" and "EPT", all
contrary to POSIX. Also, though not required by POSIX these names now use US
federal rules rather than rules of places like New York, reverting to 2024a
behavior. This change affects only timestamps before 1966-10-30 at 01:00
standard time.

Other data changes

The temporary hacks used for North American timekeeping changes now work around
a libstdc++ std::chrono bug in GCC 14.1-14.4, 15.1-15.2, and 16.1; see GCC bug
124851. This data change does not affect TZif files or timestamps. The change
does not work around the related but less serious GCC bugs 116110 and 124513.
These GCC bugs are all fixed in GCC 16.2.

Changes to documentation

URLs for release tarballs in tz-link.html have been updated to reflect their new
canonical URLs on data.iana.org.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 46e9436a-986d-4d1c-8edf-828268243bdd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}