Skip to content

chore(deps): update dependency tzdata to v2026.5 - #290

Merged
dpieski merged 1 commit into
mainfrom
renovate/tzdata-2026.x
Oct 5, 2026
Merged

dpieski merged 1 commit into
mainfrom
renovate/tzdata-2026.x

Conversation

@renovate

@renovate renovate Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
tzdata ==2026.4 → ==2026.5 age adoption passing confidence

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.


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.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, straightforward dependency pin bump.

What was reviewed: confirmed the diff is limited to the single tzdata==2026.4 to 2026.5 line change in requirements.txt and requirements-dev.txt, with matching comment blocks (pyproject.toml references) left intact. No other dependencies, pins, or code were touched.

Extended reasoning...

Diff touches only requirements.txt and requirements-dev.txt, bumping the tzdata pin from 2026.4 to 2026.5 (a Renovate-generated lockfile update for a timezone database release). No application code, auth, crypto, or other security-sensitive surface is touched. The change is minimal, mechanical, and self-contained, matching the described content exactly, so this is safe to approve without further human review.

@dpieski
dpieski merged commit 9797fbc into main Oct 5, 2026
11 checks passed
@renovate
renovate Bot deleted the renovate/tzdata-2026.x branch October 5, 2026 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant