Skip to content

Update tzdata to version 2026c#145

Merged
StanFromIreland merged 4 commits into
masterfrom
updates/update_2026c
Jul 10, 2026
Merged

Update tzdata to version 2026c#145
StanFromIreland merged 4 commits into
masterfrom
updates/update_2026c

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Version 2026.3

Upstream version 2026c released 2026-07-08T17:23:58+00:00

Briefly:

Alberta moved to permanent -06 on 2026-06-18. Morocco moves to permanent +00 on
2026-09-20. More integer overflow bugs have been fixed in zic.

Changes to future timestamps

Alberta’s 2026-03-08 spring forward was its last foreseeable clock change, as it
moved to permanent -06 thereafter. (Thanks to Roozbeh Pournader and others.)
Model this with its traditional abbreviation CST. Although the change to
permanent -06 legally took place on 2026-06-18, temporarily model the change to
occur on 2026-11-01 at 02:00 instead, for the same reason we introduced a
similarly temporary hack for British Columbia in 2026b.

Although another TZDB release will likely be needed soon because Northwest
Territories will likely follow Alberta, the legal formalities have not yet taken
place.

Morocco plans to move back to permanent UTC, without daylight saving time
transitions, on 2026-09-20 at 02:00. This also affects Western Sahara.

Changes to commentary

Northwest Territories is expected to move to permanent -06 prior to 2026-11-01
02:00, when clocks would otherwise fall back. (Thanks to Tim Parenti and James
Bellaire.) Model this with its traditional abbreviation CST. Unfortunately the
change is not yet official, so it is currently present only as comments that can
be uncommented as needed.

# Version 2026.3
Upstream version 2026c released 2026-07-08T17:23:58+00:00

## Briefly:

Alberta moved to permanent -06 on 2026-06-18. Morocco moves to permanent +00 on
2026-09-20. More integer overflow bugs have been fixed in zic.

## Changes to future timestamps

Alberta’s 2026-03-08 spring forward was its last foreseeable clock change, as it
moved to permanent -06 thereafter.  (Thanks to Roozbeh Pournader and others.)
Model this with its traditional abbreviation CST.  Although the change to
permanent -06 legally took place on 2026-06-18, temporarily model the change to
occur on 2026-11-01 at 02:00 instead, for the same reason we introduced a
similarly temporary hack for British Columbia in 2026b.

Although another TZDB release will likely be needed soon because Northwest
Territories will likely follow Alberta, the legal formalities have not yet taken
place.

Morocco plans to move back to permanent UTC, without daylight saving time
transitions, on 2026-09-20 at 02:00.  This also affects Western Sahara.

## Changes to commentary

Northwest Territories is expected to move to permanent -06 prior to 2026-11-01
02:00, when clocks would otherwise fall back.  (Thanks to Tim Parenti and James
Bellaire.)  Model this with its traditional abbreviation CST.  Unfortunately the
change is not yet official, so it is currently present only as comments that can
be uncommented as needed.
@github-actions github-actions Bot added the automatic-updates Bot-created automatic data updates label Jul 8, 2026
@StanFromIreland StanFromIreland self-assigned this Jul 8, 2026
@StanFromIreland

Copy link
Copy Markdown
Member

Created tag 2026.3rc0.

@StanFromIreland

Copy link
Copy Markdown
Member

I think I need to push a new tag, IIRC the workflows are locked to the time it was created.

@StanFromIreland

Copy link
Copy Markdown
Member

Pushed 2026.3rc1.

@StanFromIreland

Copy link
Copy Markdown
Member

Oh crap, I forgot to update the branch. Well that was all for nothing.

@StanFromIreland

Copy link
Copy Markdown
Member

Alright, 2026.3rc2 has been successfully released to TestPyPI: https://test.pypi.org/project/tzdata/2026.3rc0/ (It's misaligned as I didn't update the version in this PR)

@StanFromIreland StanFromIreland left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Release preparation.

Comment thread src/tzdata/__init__.py Outdated
Comment thread VERSION Outdated
Comment thread NEWS.md
@StanFromIreland StanFromIreland marked this pull request as draft July 9, 2026 19:37
@StanFromIreland StanFromIreland marked this pull request as ready for review July 10, 2026 08:34
Co-authored-by: Stan Ulbrych <stan@python.org>

@StanFromIreland StanFromIreland left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

Tests pass and did a manual inspection. Fixed the NEWS.md issue by adding the missing news.d/2026b.md (I presume it was omitted as the last tzdb release forgot to bump the version?).

@StanFromIreland StanFromIreland merged commit a442794 into master Jul 10, 2026
37 checks passed
@StanFromIreland StanFromIreland deleted the updates/update_2026c branch July 10, 2026 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automatic-updates Bot-created automatic data updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants