GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Update tzdata to version 2026e by github-actions[bot] · Pull Request #154 · python/tzdata

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@actions-user
Update tzdata to version 2026e
7bb0fbe
# 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.
@github-actions github-actions Bot added the automatic-updates Bot-created automatic data updates label Sep 30, 2026
@StanFromIreland StanFromIreland self-assigned this Sep 30, 2026
StanFromIreland
StanFromIreland approved these changes Sep 30, 2026
View reviewed changes

@StanFromIreland StanFromIreland left a comment

Copy link
Copy Markdown
Member

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

LGTM

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread VERSION Resolved

Uh oh!

There was an error while loading. Please reload this page.

Comment thread src/tzdata/__init__.py Resolved

Uh oh!

There was an error while loading. Please reload this page.

@StanFromIreland
StanFromIreland deployed to release September 30, 2026 15:20 — with GitHub Actions
View deployment
@StanFromIreland

StanFromIreland commented Sep 30, 2026

Copy link
Copy Markdown
Member

Inspected the release on test-pypi, everything looks good, so I'm going to land this.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@StanFromIreland
Bump version number
da0215f
Co-authored-by: Stan Ulbrych <[email protected]>
@StanFromIreland
StanFromIreland merged commit 9493aab into master Sep 30, 2026
37 checks passed

Uh oh!

There was an error while loading. Please reload this page.

@StanFromIreland
StanFromIreland deleted the updates/update_2026e branch September 30, 2026 16:28
@hamza-haydar hamza-haydar mentioned this pull request Sep 30, 2026
Alberta and related Canadian time zone changes (2026) - planned Moment-Timezone / IANA data update? moment/moment-timezone#1163
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@StanFromIreland StanFromIreland StanFromIreland approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

@StanFromIreland StanFromIreland

Labels

automatic-updates Bot-created automatic data updates

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@StanFromIreland @actions-user
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.