django-tinytools/django-tinyuser
Template
2
0
Fork 0
Code Issues Pull requests 10 Projects Releases Packages Wiki Activity Actions

Update dependency tzdata to v2026.3 #28

Open
bot.renovate wants to merge 1 commit from renovate/tzdata-2026.x into main
pull from: renovate/tzdata-2026.x
merge into: django-tinytools:main
Conversation 0 Commits 1 Files changed 3 +3 -3
bot.renovate commented 2026-07-26 03:11:07 +02:00
Member
Copy link

This PR contains the following updates:

Package Update Change
tzdata minor ==2026.2 → ==2026.3

Release Notes

python/tzdata (tzdata)

v2026.3: : Release of upstream tzdata 2026c

Compare Source

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.

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 has been generated by Mend Renovate.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [tzdata](https://github.com/python/tzdata) | minor | `==2026.2` → `==2026.3` | --- ### Release Notes <details> <summary>python/tzdata (tzdata)</summary> ### [`v2026.3`](https://github.com/python/tzdata/releases/tag/2026.3): : Release of upstream tzdata 2026c [Compare Source](https://github.com/python/tzdata/compare/2026.2...2026.3) ##### 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. </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNjEuNCIsInVwZGF0ZWRJblZlciI6IjQzLjI2MS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/tzdata-2026.x:renovate/tzdata-2026.x
git switch renovate/tzdata-2026.x

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff renovate/tzdata-2026.x
git switch renovate/tzdata-2026.x
git rebase main
git switch main
git merge --ff-only renovate/tzdata-2026.x
git switch renovate/tzdata-2026.x
git rebase main
git switch main
git merge --no-ff renovate/tzdata-2026.x
git switch main
git merge --squash renovate/tzdata-2026.x
git switch main
git merge --ff-only renovate/tzdata-2026.x
git switch main
git merge renovate/tzdata-2026.x
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
django-tinytools/django-tinyuser!28
No description provided.