Skip to content

Update dependency tzdata to v2026.4 - #1135

Open
red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/tzdata-2026.x
Open

red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/tzdata-2026.x

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
tzdata ==2026.3==2026.4 age confidence

Release Notes

python/tzdata (tzdata)

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

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@sourcery-ai

sourcery-ai Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the pinned Python tzdata dependency from 2026.3 to 2026.4, bringing current upstream timezone rules and historical corrections into the backend. Review the dependency-only change and verify the test suite, with particular attention to timezone-sensitive behavior.

File-Level Changes

Change Details Files
Pin the Python timezone database dependency to the latest upstream release.
  • Update tzdata from 2026.3 to 2026.4.
  • Incorporate upstream tzdata 2026d timezone and historical data corrections, including the Northwest Territories’ permanent UTC−06 transition.
backend/requirements-pinned.txt

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

@codecov

codecov Bot commented Sep 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.42%. Comparing base (b35aa46) to head (0acb9d8).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1135   +/-   ##
=======================================
  Coverage   87.42%   87.42%           
=======================================
  Files          63       63           
  Lines        3737     3737           
  Branches      697      697           
=======================================
  Hits         3267     3267           
  Misses        262      262           
  Partials      208      208           

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 22b3a86...0acb9d8. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

0 participants