wirehack7/DiscordStreamBot
1
0
Fork 0
Code Issues 1 Pull requests 9 Packages 1 Activity Actions

chore(deps): Update dependency tzdata to v2026 #7

Open
Renovate wants to merge 1 commit from renovate/tzdata-2026.x into master
pull from: renovate/tzdata-2026.x
merge into: wirehack7:master
Conversation 1 Commits 1 Files changed 1 +1 -1
Renovate commented 2026-06-22 01:02:17 +02:00
Collaborator
Copy link

This PR contains the following updates:

Package Change Age Confidence
tzdata ==2025.2 → ==2026.3 age confidence

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.

v2026.2: : Release of upstream tzdata 2026b

Compare Source

Version 2026.2

Upstream version 2026b released 2026-04-23T06:06:43+00:00

Briefly:

British Columbia moved to permanent -07 on 2026-03-09. Some more overflow bugs
have been fixed in zic.

Changes to future timestamps

British Columbia’s 2026-03-08 spring forward was its last foreseeable clock
change, as it moved to permanent -07 thereafter. (Thanks to Arthur David Olson.)
Although the change to permanent -07 legally took place on 2026-03-09,
temporarily model the change to occur on 2026-11-01 at 02:00 instead. This
works around a limitation in CLDR v48.2 (2026-03-17). This temporary hack is
planned to be removed after CLDR is fixed.

v2026.1: : Release of upstream tzdata 2026a

Compare Source

Version 2026.1

Upstream version 2026a released 2026-03-02T06:59:49+00:00

Briefly:

Moldova has used EU transition times since 2022. The "right" TZif files are no
longer installed by default. -DTZ_RUNTIME_LEAPS=0 disables runtime support for
leap seconds. TZif files are no longer limited to 50 bytes of abbreviations. zic
is no longer limited to 50 leap seconds. Several integer overflow bugs have been
fixed.

Changes to past and future timestamps

Since 2022 Moldova has observed EU transition times, that is, it has sprung
forward at 03:00, not 02:00, and has fallen back at 04:00, not 03:00. (Thanks
to Heitor David Pinto.)

Changes to data

Remove Europe/Chisinau from zonenow.tab, as it now agrees with Europe/Athens for
future timestamps.

v2025.3: : Release of upstream tzdata 2025c

Compare Source

Version 2025.3

Upstream version 2025c released 2025-12-10T22:42:37+00:00

Briefly:

Several code changes for compatibility with FreeBSD.

Changes to past timestamps

Baja California agreed with California’s DST rules in 1953 and in 1961 through
1975, instead of observing standard time all year. (Thanks to Alois Treindl.)

Changes to commentary

The leapseconds file contains commentary about the IERS and NIST last-modified
and expiration timestamps for leap second data. (Thanks to Judah Levine.)

Commentary now also uses characters from the set –‘’“”•≤ as this can be useful
and should work with current applications. This also affects data in
iso3166.tab and zone1970.tab, which now contain strings like “Côte d’Ivoire”
instead of “Côte d'Ivoire”.

Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • "before 6am on monday"
  • 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 CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [tzdata](https://github.com/python/tzdata) | `==2025.2` → `==2026.3` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/tzdata/2026.3?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/tzdata/2025.2/2026.3?slim=true) | --- ### 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. ### [`v2026.2`](https://github.com/python/tzdata/releases/tag/2026.2): : Release of upstream tzdata 2026b [Compare Source](https://github.com/python/tzdata/compare/2026.1...2026.2) ### Version 2026.2 Upstream version 2026b released 2026-04-23T06:06:43+00:00 #### Briefly: British Columbia moved to permanent -07 on 2026-03-09. Some more overflow bugs have been fixed in zic. #### Changes to future timestamps British Columbia’s 2026-03-08 spring forward was its last foreseeable clock change, as it moved to permanent -07 thereafter. (Thanks to Arthur David Olson.) Although the change to permanent -07 legally took place on 2026-03-09, temporarily model the change to occur on 2026-11-01 at 02:00 instead. This works around a limitation in CLDR v48.2 (2026-03-17). This temporary hack is planned to be removed after CLDR is fixed. ### [`v2026.1`](https://github.com/python/tzdata/releases/tag/2026.1): : Release of upstream tzdata 2026a [Compare Source](https://github.com/python/tzdata/compare/2025.3...2026.1) ### Version 2026.1 Upstream version 2026a released 2026-03-02T06:59:49+00:00 #### Briefly: Moldova has used EU transition times since 2022. The "right" TZif files are no longer installed by default. -DTZ\_RUNTIME\_LEAPS=0 disables runtime support for leap seconds. TZif files are no longer limited to 50 bytes of abbreviations. zic is no longer limited to 50 leap seconds. Several integer overflow bugs have been fixed. #### Changes to past and future timestamps Since 2022 Moldova has observed EU transition times, that is, it has sprung forward at 03:00, not 02:00, and has fallen back at 04:00, not 03:00. (Thanks to Heitor David Pinto.) #### Changes to data Remove Europe/Chisinau from zonenow\.tab, as it now agrees with Europe/Athens for future timestamps. ### [`v2025.3`](https://github.com/python/tzdata/releases/tag/2025.3): : Release of upstream tzdata 2025c [Compare Source](https://github.com/python/tzdata/compare/2025.2...2025.3) ### Version 2025.3 Upstream version 2025c released 2025-12-10T22:42:37+00:00 #### Briefly: Several code changes for compatibility with FreeBSD. #### Changes to past timestamps Baja California agreed with California’s DST rules in 1953 and in 1961 through 1975, instead of observing standard time all year. (Thanks to Alois Treindl.) #### Changes to commentary The leapseconds file contains commentary about the IERS and NIST last-modified and expiration timestamps for leap second data. (Thanks to Judah Levine.) Commentary now also uses characters from the set –‘’“”•≤ as this can be useful and should work with current applications. This also affects data in iso3166.tab and zone1970.tab, which now contain strings like “Côte d’Ivoire” instead of “Côte d'Ivoire”. </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/Berlin) - Branch creation - "before 6am on monday" - 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 CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMzQuMCIsInVwZGF0ZWRJblZlciI6IjQ0LjQuMCIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSJdfQ==-->
chore(deps): Update dependency tzdata to v2026
Some checks failed
Build and Push Docker Image / build (pull_request) Successful in -5m33s
Details
PR Tests / test (pull_request) Failing after 29s
Details
7f3156e706
forgejo-actions commented 2026-06-22 01:02:46 +02:00
Copy link

CI Results

Check Status
Ruff ✅
Pylint (9.93/10) ❌
Config ✅
Imports ✅
Pylint output 
************* Module func.watcher
src/func/watcher.py:115:15: W0718: Catching too general exception Exception (broad-exception-caught)
src/func/watcher.py:133:15: W0718: Catching too general exception Exception (broad-exception-caught)

-----------------------------------
Your code has been rated at 9.93/10

Updated: 2026-07-10 09:05 UTC

<!-- ci-results --> ## CI Results | Check | Status | |---|---| | Ruff | ✅ | | Pylint (9.93/10) | ❌ | | Config | ✅ | | Imports | ✅ | <details><summary>Pylint output</summary> ``` ************* Module func.watcher src/func/watcher.py:115:15: W0718: Catching too general exception Exception (broad-exception-caught) src/func/watcher.py:133:15: W0718: Catching too general exception Exception (broad-exception-caught) ----------------------------------- Your code has been rated at 9.93/10 ``` </details> _Updated: 2026-07-10 09:05 UTC_
Renovate force-pushed renovate/tzdata-2026.x from 7f3156e706
Some checks failed
Build and Push Docker Image / build (pull_request) Successful in -5m33s
Details
PR Tests / test (pull_request) Failing after 29s
Details
to 10af88e21e
Some checks failed
Build and Push Docker Image / build (pull_request) Successful in 1m17s
Details
PR Tests / test (pull_request) Failing after 1m24s
Details
2026-07-10 11:04:07 +02:00 Compare
Some checks failed
Build and Push Docker Image / build (pull_request) Successful in 1m17s
Details
PR Tests / test (pull_request) Failing after 1m24s
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
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 master
git merge --no-ff renovate/tzdata-2026.x
git switch renovate/tzdata-2026.x
git rebase master
git switch master
git merge --ff-only renovate/tzdata-2026.x
git switch renovate/tzdata-2026.x
git rebase master
git switch master
git merge --no-ff renovate/tzdata-2026.x
git switch master
git merge --squash renovate/tzdata-2026.x
git switch master
git merge --ff-only renovate/tzdata-2026.x
git switch master
git merge renovate/tzdata-2026.x
git push origin master
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
2 participants
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
wirehack7/DiscordStreamBot!7
No description provided.