kfickel/streamd
1
0
Fork 0
Code Issues 6 Pull requests 2 Projects 1 Releases 7 Wiki Activity Actions

fix(deps): update rust crate chrono-tz to 0.10 #78

Merged
renovate-bot merged 1 commit from renovate/chrono-tz-0.x into main 2026-04-03 02:12:18 +02:00
Conversation 0 Commits 1 Files changed 2 +7 -63
renovate-bot commented 2026-04-03 02:06:42 +02:00
Collaborator
Copy link

This PR contains the following updates:

Package Type Update Change
chrono-tz dependencies minor 0.9 → 0.10

Release Notes

chronotope/chrono-tz (chrono-tz)

v0.10.4

Compare Source

What's Changed

v0.10.3: 0.10.3

Compare Source

What's Changed

v0.10.2: 0.10.2

Compare Source

What's Changed

v0.10.1: 0.10.1

Compare Source

What's Changed

v0.10.0: chrono-tz v0.10.0: 2024b

Compare Source

TZDB version 2024b (2024-09-05).

Changes

  • Make OffsetName::abbreviation return an Option.
    This reflects that numeric values such as +11 are no longer encoded in the upstream TZDB as abbreviations (#​185).

TZDB 2024b

The 2024b release of the tz code and data is available.

This release is prompted by the accumulated weight of many non-urgent changes to both code and data. It changes one timestamp abbreviation, for the long-obsolete System V setting TZ='MET'; see below. Otherwise, the timestamps affected by this release all predate April 2008, so you can skip this release if your application uses only tzdata and does not use older timestamps.

This release contains the following changes:

Briefly:

Improve historical data for Mexico, Mongolia, and Portugal.
System V names are now obsolescent.
The main data form now uses %z.
The code now conforms to RFC 8536 for early timestamps.
Support POSIX.1-2024, which removes asctime_r and ctime_r.
Assume POSIX.2-1992 or later for shell scripts.
SUPPORT_C89 now defaults to 1.

Changes to past timestamps

Asia/Choibalsan is now an alias for Asia/Ulaanbaatar rather than being a separate Zone with differing behavior before April 2008. This seems better given our wildly conflicting information about Mongolia's time zone history. (Thanks to Heitor David Pinto.)

Historical transitions for Mexico have been updated based on official Mexican decrees. The affected timestamps occur during the years 1921-1927, 1931, 1945, 1949-1970, and 1981-1997. The affected zones are America/Bahia_Banderas, America/Cancun, America/Chihuahua, America/Ciudad_Juarez, America/Hermosillo, America/Mazatlan, America/Merida, America/Mexico_City, America/Monterrey, America/Ojinaga, and America/Tijuana. (Thanks to Heitor David Pinto.)

Historical transitions for Portugal, represented by Europe/Lisbon, Atlantic/Azores, and Atlantic/Madeira, have been updated based on a close reading of old Portuguese legislation, replacing previous data mainly originating from Whitman and Shanks & Pottenger. These changes affect a few transitions in 1917-1921, 1924, and 1940 throughout these regions by a few hours or days, and various timestamps between 1977 and 1993 depending on the region. In particular, the Azores and Madeira did not observe DST from 1977 to 1981. Additionally, the adoption of standard zonal time in former Portuguese colonies have been adjusted: Africa/Maputo in 1909, and Asia/Dili by 22 minutes at the start of 1912. (Thanks to Tim Parenti.)

Changes to past tm_isdst flags

The period from 1966-04-03 through 1966-10-02 in Portugal is now modeled as DST, to more closely reflect how contemporaneous changes in law entered into force.

Changes to data

Names present only for compatibility with UNIX System V (last released in the 1990s) have been moved to 'backward'. These names, which for post-1970 timestamps mostly just duplicate data of geographical names, were confusing downstream uses. Names moved to 'backward' are now links to geographical names. This affects behavior for TZ='EET' for some pre-1981 timestamps, for TZ='CET' for some pre-1947 timestamps, and for TZ='WET' for some pre-1996 timestamps. Also, TZ='MET' now behaves like TZ='CET' and so uses the abbreviation "CET" rather than "MET". Those needing the previous TZDB behavior, which does not match any real-world clocks, can find the old entries in 'backzone'. (Problem reported by Justin Grant.)

The main source files' time zone abbreviations now use %z, supported by zic since release 2015f and used in vanguard form since release 2022b. For example, America/Sao_Paulo now contains the zone continuation line "-3:00 Brazil %z", which is less error prone than the old "-3:00 Brazil -03/-02". This does not change the represented data: the generated TZif files are unchanged. Rearguard form still avoids %z, to support obsolescent parsers.

Asia/Almaty has been removed from zonenow.tab as it now agrees with Asia/Tashkent for future timestamps, due to Kazakhstan's 2024-02-29 time zone change. Similarly, America/Scoresbysund has been removed, as it now agrees with America/Nuuk due to its 2024-03-31 time zone change.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [chrono-tz](https://github.com/chronotope/chrono-tz) | dependencies | minor | `0.9` → `0.10` | --- ### Release Notes <details> <summary>chronotope/chrono-tz (chrono-tz)</summary> ### [`v0.10.4`](https://github.com/chronotope/chrono-tz/releases/tag/v0.10.4) [Compare Source](https://github.com/chronotope/chrono-tz/compare/v0.10.3...v0.10.4) #### What's Changed - Fix chrono-tz-build dep on parse-zoneinfo by [@&#8203;GoldsteinE](https://github.com/GoldsteinE) in [#&#8203;198](https://github.com/chronotope/chrono-tz/pull/198) - Upgrade `phf*` to v0.12 by [@&#8203;paolobarbolini](https://github.com/paolobarbolini) in [#&#8203;200](https://github.com/chronotope/chrono-tz/pull/200) - Correctly handle transitions specified in UTC by [@&#8203;robertbastian](https://github.com/robertbastian) in [#&#8203;204](https://github.com/chronotope/chrono-tz/pull/204) - Use prebuilt data when built with default features by [@&#8203;djc](https://github.com/djc) in [#&#8203;207](https://github.com/chronotope/chrono-tz/pull/207) ### [`v0.10.3`](https://github.com/chronotope/chrono-tz/releases/tag/v0.10.3): 0.10.3 [Compare Source](https://github.com/chronotope/chrono-tz/compare/v0.10.2...v0.10.3) #### What's Changed - Check MSRV in CI by [@&#8203;djc](https://github.com/djc) in [#&#8203;196](https://github.com/chronotope/chrono-tz/pull/196) - Trigger CI on merge groups by [@&#8203;djc](https://github.com/djc) in [#&#8203;197](https://github.com/chronotope/chrono-tz/pull/197) ### [`v0.10.2`](https://github.com/chronotope/chrono-tz/releases/tag/v0.10.2): 0.10.2 [Compare Source](https://github.com/chronotope/chrono-tz/compare/v0.10.1...v0.10.2) #### What's Changed - Add gap\_info\_from\_local\_datetime to get information about a gap by [@&#8203;acrrd](https://github.com/acrrd) in [#&#8203;188](https://github.com/chronotope/chrono-tz/pull/188) - Bump to 0.10.2 with 2025b by [@&#8203;djc](https://github.com/djc) in [#&#8203;194](https://github.com/chronotope/chrono-tz/pull/194) ### [`v0.10.1`](https://github.com/chronotope/chrono-tz/releases/tag/v0.10.1): 0.10.1 [Compare Source](https://github.com/chronotope/chrono-tz/compare/v0.10.0...v0.10.1) #### What's Changed - Fix verify publish ci by [@&#8203;acrrd](https://github.com/acrrd) in [#&#8203;189](https://github.com/chronotope/chrono-tz/pull/189) - Prepare 0.10.1 for 2025a by [@&#8203;djc](https://github.com/djc) in [#&#8203;190](https://github.com/chronotope/chrono-tz/pull/190) ### [`v0.10.0`](https://github.com/chronotope/chrono-tz/releases/tag/v0.10.0): chrono-tz v0.10.0: 2024b [Compare Source](https://github.com/chronotope/chrono-tz/compare/v0.9.0...v0.10.0) **TZDB** version 2024b (2024-09-05). #### Changes - Make `OffsetName::abbreviation` return an `Option`. This reflects that numeric values such as `+11` are no longer encoded in the upstream TZDB as abbreviations ([#&#8203;185](https://github.com/chronotope/chrono-tz/issues/185)). #### TZDB 2024b > The 2024b release of the tz code and data is available. > > This release is prompted by the accumulated weight of many non-urgent changes to both code and data. It changes one timestamp abbreviation, for the long-obsolete System V setting TZ='MET'; see below. Otherwise, the timestamps affected by this release all predate April 2008, so you can skip this release if your application uses only tzdata and does not use older timestamps. > > This release contains the following changes: > > ### Briefly: > > Improve historical data for Mexico, Mongolia, and Portugal. > System V names are now obsolescent. > The main data form now uses %z. > The code now conforms to RFC 8536 for early timestamps. > Support POSIX.1-2024, which removes asctime\_r and ctime\_r. > Assume POSIX.2-1992 or later for shell scripts. > SUPPORT\_C89 now defaults to 1. > > ### Changes to past timestamps > > Asia/Choibalsan is now an alias for Asia/Ulaanbaatar rather than being a separate Zone with differing behavior before April 2008. This seems better given our wildly conflicting information about Mongolia's time zone history. (Thanks to Heitor David Pinto.) > > Historical transitions for Mexico have been updated based on official Mexican decrees. The affected timestamps occur during the years 1921-1927, 1931, 1945, 1949-1970, and 1981-1997. The affected zones are America/Bahia\_Banderas, America/Cancun, America/Chihuahua, America/Ciudad\_Juarez, America/Hermosillo, America/Mazatlan, America/Merida, America/Mexico\_City, America/Monterrey, America/Ojinaga, and America/Tijuana. (Thanks to Heitor David Pinto.) > > Historical transitions for Portugal, represented by Europe/Lisbon, Atlantic/Azores, and Atlantic/Madeira, have been updated based on a close reading of old Portuguese legislation, replacing previous data mainly originating from Whitman and Shanks & Pottenger. These changes affect a few transitions in 1917-1921, 1924, and 1940 throughout these regions by a few hours or days, and various timestamps between 1977 and 1993 depending on the region. In particular, the Azores and Madeira did not observe DST from 1977 to 1981. Additionally, the adoption of standard zonal time in former Portuguese colonies have been adjusted: Africa/Maputo in 1909, and Asia/Dili by 22 minutes at the start of 1912. (Thanks to Tim Parenti.) > > ### Changes to past tm\_isdst flags > > The period from 1966-04-03 through 1966-10-02 in Portugal is now modeled as DST, to more closely reflect how contemporaneous changes in law entered into force. > > ### Changes to data > > Names present only for compatibility with UNIX System V (last released in the 1990s) have been moved to 'backward'. These names, which for post-1970 timestamps mostly just duplicate data of geographical names, were confusing downstream uses. Names moved to 'backward' are now links to geographical names. This affects behavior for TZ='EET' for some pre-1981 timestamps, for TZ='CET' for some pre-1947 timestamps, and for TZ='WET' for some pre-1996 timestamps. Also, TZ='MET' now behaves like TZ='CET' and so uses the abbreviation "CET" rather than "MET". Those needing the previous TZDB behavior, which does not match any real-world clocks, can find the old entries in 'backzone'. (Problem reported by Justin Grant.) > > The main source files' time zone abbreviations now use %z, supported by zic since release 2015f and used in vanguard form since release 2022b. For example, America/Sao\_Paulo now contains the zone continuation line "-3:00 Brazil %z", which is less error prone than the old "-3:00 Brazil -03/-02". This does not change the represented data: the generated TZif files are unchanged. Rearguard form still avoids %z, to support obsolescent parsers. > > Asia/Almaty has been removed from zonenow\.tab as it now agrees with Asia/Tashkent for future timestamps, due to Kazakhstan's 2024-02-29 time zone change. Similarly, America/Scoresbysund has been removed, as it now agrees with America/Nuuk due to its 2024-03-31 time zone change. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMDIuOSIsInVwZGF0ZWRJblZlciI6IjQzLjEwMi45IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate-bot added 1 commit 2026-04-03 02:06:42 +02:00
fix(deps): update rust crate chrono-tz to 0.10
All checks were successful
Continuous Integration / Lint, Check & Test (push) Successful in 2m46s
Details
Continuous Integration / Build Package (push) Successful in 3m10s
Details
1bd661a2a6
renovate-bot scheduled this pull request to auto merge when all checks succeed 2026-04-03 02:06:42 +02:00
renovate-bot merged commit 6453ef7c2a into main 2026-04-03 02:12:18 +02:00
renovate-bot deleted branch renovate/chrono-tz-0.x 2026-04-03 02:12:19 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
planned

The feature is ready to be implemented by an AI agent

No labels
planned
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.

Reference: kfickel/streamd#78
No description provided.
Delete branch "renovate/chrono-tz-0.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?