Update tzdata to version '2025c' #118
Open
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.
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”.