[tz-announce] 2026c release of tz code and data available
The 2026c release of the tz code and data is available. This release’s main urgency is Alberta’s decision to stop changing its clocks and stay on permanent UTC-06, which has a practical effect starting 2026-11-01 at 02:00. Like the similar British Columbia changes in the previous release, there will likely be problems downstream as CLDR’s latest release cannot handle it as specified. So we’re releasing now so that downstream has some time to test and adjust. Also, Morocco is moving to permanent UTC on 2026-09-20. This will likely cause fewer problems among downstream CLDR users. Although quite possibly we’ll soon need another TZDB release to accommodate similar changes planned for Northwest Territories, these changes have not been formalized yet. This release contains the following changes: 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 code zic no longer overflows integers when processing outlandish input like ‘Zone Ouch 0 - LMT 9223372036854775807’, ‘Zone Ouch 0 2562047788015215 LMT’, ‘Zone Ouch -2562047788015215:30:08 - LMT’, and ‘Zone Ouch -2562047788015215:30:08 - %%z’. This avoids undefined behavior in C. (Problems reported by Naveed Khan.) On platforms that have EFTYPE, tzalloc now fails with errno set to EFTYPE, not EINVAL, if it detects that the TZif file has an invalid format or is not a regular file. Formerly it did this only on NetBSD, and only when the file was not a regular file. Unprivileged programs no longer require TZif files to be regular files or reject relative names containing ".." components. This reverts to the more-permissive 2025b behavior, as the stricter behavior did not catch on in FreeBSD. zic now reports any failure to remove a temporary file when cleaning up after a previous failure. (Problem reported by Tom Lane.) 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. Changes to build procedure The undocumented ‘typecheck’ Makefile check rule has been removed. It stopped working in 2025a and evidently nobody noticed. The rule was superseded by ‘check_time_t_alternatives’ in 2013d. Here are links to the release files: https://www.iana.org/time-zones/repository/releases/tzcode2026c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2026c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2026c.tar.lz The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed: https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above. Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message. This release corresponds to commit 71f28b9ab3b67c0f9466803f6151812d4fc8e357 dated 2026-07-08 10:23:58 -0700 and tagged '2026c' in the development GitHub repository at <https://github.com/eggert/tz>. Here are the SHA-512 checksums for the release files: ad1aadf26b9aaca487a4f780d7a8ebf1d7383472ce587b06cb63852d4eb030dbd190b537e393e75d59530318581e9d3f492ff5f97bbac78f548d0755c4f7257f tzcode2026c.tar.gz e0b4b7044b66fbc27bc21d13d18063abcdf78ab58d5ba5fd64bd1a88d86e9d495f45add4d8e65bb6c40249f9c94ca29b72c8ebba8d0e4c468f2965ac77932ef0 tzdata2026c.tar.gz 3e5aec7d93522efc875fc8af553f78029677aaa9be8db396c862d687bdedb930379ba6246b33a15c5fb3a76d24e937dac4f4f66d6f9edf69a668bb21e9eeada7 tzdb-2026c.tar.lz Here are GPG digital signatures for the release files: -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmpOiy0ACgkQ7ZfpDmKq fjRS/hAApD5lVCI/pMXFa6G1WT/Lx3Fydw0Frzo/uCeRtopN+HwLt7e5mwsWQBPe ju7nUs6Zg434ZlY7Rt/xKDPqFZnWmRdNqselkNsUpWi7ajm3VWm6TwJU7Gltkjbo 34DVY7Mn2Pmvma9bsPj1LJCqi+lsILVTobGZhGxh6NcgZ+CUFnVJKTWenDFuSzGA QltBeA74BH0zxIhCnqRjwaUtF1IS9WaX52I58k7llPn05AkGH8po+mkaz6jmqF+N BoL8lgTbNqkDzOaiVY0u2fjx6SoXW3tHPywpTGJeyfgD4KbYQOustw8zMXEANR6I W4M1p1j1aNo8Ss2ZXsNDDP9ZSAD3jRmNV18V4vB/cADff6K/Y/Phq8mHTiKjjS4W 4Fy54avRkk3HEgboytA6R7vwD1naB6L1FE4SM3TbIXO22BeHs4qhBjSRB3Wfk+1u AuGQsCNORi8GXYRSLPUm4ekss9WTU46JXqwa7yHPQH6sKRiHyFci4V1qk0Hhlh2Z 2DCURjXhI/9L+blozsZRZg3bxDN32iFEZAdE+iMmW0VPP39VrlL1gH/GisORzKL0 XCtIducsD7ZvV/cvCADUBwy3zgatXh0VaP2ozWHnnt/9hMVT6it6/2GMY0vY/D61 TUw2Rfa2P3y7IpRfGcT24kFjKv8rxx4A8mM9HndW/fYkUN2O3W4= =kK0H -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmpOiy0ACgkQ7ZfpDmKq fjR6yA/9H1+9KOGi6LIatyM5HSQb6UrOQ5X+Zs1SrBZk95yXBcgYRU6Ycfy3gGM8 +TWBKmMDiN3F1kRBeNgu4h/BAnXkpND50qyyLXKl5ztYdbRaZXZCMizPB7px7+CG YQuOErpS//MEEmtzKNRQBdgOAHv+eAMFIn6keLl8RbIeS1sQ2gewto2BeIDyYSx/ IuDNikI4/6ogyJYaxEKQgmpV/WcPLr5m+GCvW2zzpa7n5RHwR+UyksTGwD1vbQsi +DglIW3IjrdTM5/zuXsjmCxZX2MwxL7vZ62IDiEIlZefpz+7PdROU6fFwqZLryJB bHMTJpD+tjpxIv1j/xKSXA1f6KIOALVpA5eIaPc/S4ZGc4ZAHqghwzsE62fTv/3R 5M20csuAeP5nhEeLpa1UH7+4qLg9HAosXVYfbALeJunLYSUCiBmN2/XmA4W4Q3OD btS8fvt68Lax6srHkcHWFv39doXZNWkPTPFbsWJzqWVW0vhIh1YWJWCtobZ93wGM huKVTG49JGvB8qZQAnYaZdMrIYmNI/x9YYwV9rsvcpTANTRKAHEMoz4jX7fxGjrS xjqmr2RpoDpnd1xvyXIirnn4WkQeO2OF2xhABsAvMstfZf+PAhXl7flucLH2oTNy /8ZIzbItjoFWrbXqtEwE7goMq5XcP4BGOmr+nj2EukJF7CqWkj0= =r0JP -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmpOiy4ACgkQ7ZfpDmKq fjS51g//XdOjk0dzan2ashSNf6NiJ90VuBhCJAeCPBqr3BCVOD94K1riazP1ZbnN q2ex9llB63ZXuZ52W0Q5NigP1eQ+SOzYFN1WD8bQc4uUDfhF8vCO2bAF7bFyzWPd PD+geLWT23lkDtMGFDNePHYgiaOnBvqvadRryUbiPuXTJnEb0VCFU6catuAp+bG8 HADbnFAYQosiR+O2WVvhDmVdDtbJqaPFZFILSK4J+uxD6Kf8sS0/twEm5+hmJiPE Hy7yI65yKGKDcCCp0OFu/+412ZAOgExjVdC58/IGHYit8pAzI35mMm2xfzicShCk Sj1cm8mKLDC8w6J9huqNMK+p8NW4RrjMoeJaa11vgy3ARYkqVnfNZI+YPxQO5LKB yrgw8NF5ZafJYSYR+ZmjiZWTGe/1tMoC6GRmzwfIYmaLFlAIw4fTAe4ySqRIVgKo J5u28wneVxjCbueIE1qgWWvCIvz8xVB6ytx90SPigp6FumKTJiZm2/vF/Hem/5Hk gwKFSxGRBwBIVh5uaWWJEft2nSvpG5lONo1rZ2ygPTfbczjZMDZpoxEmWIeZjQ+r LrzNaDpzxFecfLvlUMrIOr4iwH14cDwkdGtCIJ5N/7uBwLfg+7sYts4pmAVdBZxd sCbAuEN/GtkNPV4cSYnDyF0FbM4zPGbztlOxxiOQG1RtJ51rbjI= =VYnI -----END PGP SIGNATURE-----
Hi! The *version* file inside *tzdata-latest.tar.gz* for the latest version ( *2026c*) is *incorrect*. The content is *2026b* instead of *2026c*. Thank you. Fabio Brandão Senior Staff Software Engineer +55 11 99638-1613 wellhub.com Making every company a wellness company. This message (including any attachments) is confidential and is intended for exclusive use of the person/entity to whom/which it is addressed. If you have received it by mistake, please delete it from your system immediately. Non-authorized use and/or dissemination of whole or part of this message are strictly prohibited. Wellhub, or any of the companies from its group, does not guarantee the integrity and is not responsible for the content or veracity of this communication. On Wed, Jul 8, 2026 at 3:25 PM Paul Eggert via tz-announce < tz-announce@iana.org> wrote:
The 2026c release of the tz code and data is available. This release’s main urgency is Alberta’s decision to stop changing its clocks and stay on permanent UTC-06, which has a practical effect starting 2026-11-01 at 02:00. Like the similar British Columbia changes in the previous release, there will likely be problems downstream as CLDR’s latest release cannot handle it as specified. So we’re releasing now so that downstream has some time to test and adjust.
Also, Morocco is moving to permanent UTC on 2026-09-20. This will likely cause fewer problems among downstream CLDR users.
Although quite possibly we’ll soon need another TZDB release to accommodate similar changes planned for Northwest Territories, these changes have not been formalized yet.
This release contains the following changes:
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 code
zic no longer overflows integers when processing outlandish input like ‘Zone Ouch 0 - LMT 9223372036854775807’, ‘Zone Ouch 0 2562047788015215 LMT’, ‘Zone Ouch -2562047788015215:30:08 - LMT’, and ‘Zone Ouch -2562047788015215:30:08 - %%z’. This avoids undefined behavior in C. (Problems reported by Naveed Khan.)
On platforms that have EFTYPE, tzalloc now fails with errno set to EFTYPE, not EINVAL, if it detects that the TZif file has an invalid format or is not a regular file. Formerly it did this only on NetBSD, and only when the file was not a regular file.
Unprivileged programs no longer require TZif files to be regular files or reject relative names containing ".." components. This reverts to the more-permissive 2025b behavior, as the stricter behavior did not catch on in FreeBSD.
zic now reports any failure to remove a temporary file when cleaning up after a previous failure. (Problem reported by Tom Lane.)
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.
Changes to build procedure
The undocumented ‘typecheck’ Makefile check rule has been removed. It stopped working in 2025a and evidently nobody noticed. The rule was superseded by ‘check_time_t_alternatives’ in 2013d.
Here are links to the release files:
https://www.iana.org/time-zones/repository/releases/tzcode2026c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdata2026c.tar.gz https://www.iana.org/time-zones/repository/releases/tzdb-2026c.tar.lz
The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed:
https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz
Links are also available via plain HTTP, and via FTP from ftp://ftp.iana.org/tz/releases with the same basenames as above.
Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message.
This release corresponds to commit 71f28b9ab3b67c0f9466803f6151812d4fc8e357 dated 2026-07-08 10:23:58 -0700 and tagged '2026c' in the development GitHub repository at <https://github.com/eggert/tz>.
Here are the SHA-512 checksums for the release files:
ad1aadf26b9aaca487a4f780d7a8ebf1d7383472ce587b06cb63852d4eb030dbd190b537e393e75d59530318581e9d3f492ff5f97bbac78f548d0755c4f7257f
tzcode2026c.tar.gz e0b4b7044b66fbc27bc21d13d18063abcdf78ab58d5ba5fd64bd1a88d86e9d495f45add4d8e65bb6c40249f9c94ca29b72c8ebba8d0e4c468f2965ac77932ef0
tzdata2026c.tar.gz 3e5aec7d93522efc875fc8af553f78029677aaa9be8db396c862d687bdedb930379ba6246b33a15c5fb3a76d24e937dac4f4f66d6f9edf69a668bb21e9eeada7
tzdb-2026c.tar.lz
Here are GPG digital signatures for the release files:
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmpOiy0ACgkQ7ZfpDmKq fjRS/hAApD5lVCI/pMXFa6G1WT/Lx3Fydw0Frzo/uCeRtopN+HwLt7e5mwsWQBPe ju7nUs6Zg434ZlY7Rt/xKDPqFZnWmRdNqselkNsUpWi7ajm3VWm6TwJU7Gltkjbo 34DVY7Mn2Pmvma9bsPj1LJCqi+lsILVTobGZhGxh6NcgZ+CUFnVJKTWenDFuSzGA QltBeA74BH0zxIhCnqRjwaUtF1IS9WaX52I58k7llPn05AkGH8po+mkaz6jmqF+N BoL8lgTbNqkDzOaiVY0u2fjx6SoXW3tHPywpTGJeyfgD4KbYQOustw8zMXEANR6I W4M1p1j1aNo8Ss2ZXsNDDP9ZSAD3jRmNV18V4vB/cADff6K/Y/Phq8mHTiKjjS4W 4Fy54avRkk3HEgboytA6R7vwD1naB6L1FE4SM3TbIXO22BeHs4qhBjSRB3Wfk+1u AuGQsCNORi8GXYRSLPUm4ekss9WTU46JXqwa7yHPQH6sKRiHyFci4V1qk0Hhlh2Z 2DCURjXhI/9L+blozsZRZg3bxDN32iFEZAdE+iMmW0VPP39VrlL1gH/GisORzKL0 XCtIducsD7ZvV/cvCADUBwy3zgatXh0VaP2ozWHnnt/9hMVT6it6/2GMY0vY/D61 TUw2Rfa2P3y7IpRfGcT24kFjKv8rxx4A8mM9HndW/fYkUN2O3W4= =kK0H -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmpOiy0ACgkQ7ZfpDmKq fjR6yA/9H1+9KOGi6LIatyM5HSQb6UrOQ5X+Zs1SrBZk95yXBcgYRU6Ycfy3gGM8 +TWBKmMDiN3F1kRBeNgu4h/BAnXkpND50qyyLXKl5ztYdbRaZXZCMizPB7px7+CG YQuOErpS//MEEmtzKNRQBdgOAHv+eAMFIn6keLl8RbIeS1sQ2gewto2BeIDyYSx/ IuDNikI4/6ogyJYaxEKQgmpV/WcPLr5m+GCvW2zzpa7n5RHwR+UyksTGwD1vbQsi +DglIW3IjrdTM5/zuXsjmCxZX2MwxL7vZ62IDiEIlZefpz+7PdROU6fFwqZLryJB bHMTJpD+tjpxIv1j/xKSXA1f6KIOALVpA5eIaPc/S4ZGc4ZAHqghwzsE62fTv/3R 5M20csuAeP5nhEeLpa1UH7+4qLg9HAosXVYfbALeJunLYSUCiBmN2/XmA4W4Q3OD btS8fvt68Lax6srHkcHWFv39doXZNWkPTPFbsWJzqWVW0vhIh1YWJWCtobZ93wGM huKVTG49JGvB8qZQAnYaZdMrIYmNI/x9YYwV9rsvcpTANTRKAHEMoz4jX7fxGjrS xjqmr2RpoDpnd1xvyXIirnn4WkQeO2OF2xhABsAvMstfZf+PAhXl7flucLH2oTNy /8ZIzbItjoFWrbXqtEwE7goMq5XcP4BGOmr+nj2EukJF7CqWkj0= =r0JP -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEfjeSqdis99YzvBWI7ZfpDmKqfjQFAmpOiy4ACgkQ7ZfpDmKq fjS51g//XdOjk0dzan2ashSNf6NiJ90VuBhCJAeCPBqr3BCVOD94K1riazP1ZbnN q2ex9llB63ZXuZ52W0Q5NigP1eQ+SOzYFN1WD8bQc4uUDfhF8vCO2bAF7bFyzWPd PD+geLWT23lkDtMGFDNePHYgiaOnBvqvadRryUbiPuXTJnEb0VCFU6catuAp+bG8 HADbnFAYQosiR+O2WVvhDmVdDtbJqaPFZFILSK4J+uxD6Kf8sS0/twEm5+hmJiPE Hy7yI65yKGKDcCCp0OFu/+412ZAOgExjVdC58/IGHYit8pAzI35mMm2xfzicShCk Sj1cm8mKLDC8w6J9huqNMK+p8NW4RrjMoeJaa11vgy3ARYkqVnfNZI+YPxQO5LKB yrgw8NF5ZafJYSYR+ZmjiZWTGe/1tMoC6GRmzwfIYmaLFlAIw4fTAe4ySqRIVgKo J5u28wneVxjCbueIE1qgWWvCIvz8xVB6ytx90SPigp6FumKTJiZm2/vF/Hem/5Hk gwKFSxGRBwBIVh5uaWWJEft2nSvpG5lONo1rZ2ygPTfbczjZMDZpoxEmWIeZjQ+r LrzNaDpzxFecfLvlUMrIOr4iwH14cDwkdGtCIJ5N/7uBwLfg+7sYts4pmAVdBZxd sCbAuEN/GtkNPV4cSYnDyF0FbM4zPGbztlOxxiOQG1RtJ51rbjI= =VYnI -----END PGP SIGNATURE-----
On 2026-07-08 12:02, Fabio Brandão wrote:
The *version* file inside *tzdata-latest.tar.gz* for the latest version ( *2026c*) is *incorrect*. The content is *2026b* instead of *2026c*.
I'm not seeing that; see transcript below. Most likely this is related to the following text in the release announcement: "The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed". $ wget https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz --2026-07-08 12:23:24-- https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz Resolving www.iana.org (www.iana.org)... 104.18.24.232, 104.18.25.232, 2606:4700::6812:19e8, ... Connecting to www.iana.org (www.iana.org)|104.18.24.232|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://data.iana.org/time-zones/tzdata-latest.tar.gz [following] --2026-07-08 12:23:24-- https://data.iana.org/time-zones/tzdata-latest.tar.gz Resolving data.iana.org (data.iana.org)... 104.18.25.232, 104.18.24.232, 2606:4700::6812:18e8, ... Connecting to data.iana.org (data.iana.org)|104.18.25.232|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 475694 (465K) [application/x-gzip] Saving to: ‘tzdata-latest.tar.gz’ tzdata-latest.tar.g 100%[===================>] 464.54K --.-KB/s in 0.01s 2026-07-08 12:23:25 (46.3 MB/s) - ‘tzdata-latest.tar.gz’ saved [475694/475694] $ tar xf tzdata-latest.tar.gz $ cat version 2026c
Quoting Paul Eggert via tz on Wednesday July 08, 2026:
On 2026-07-08 12:02, Fabio Brandão wrote:
The *version* file inside *tzdata-latest.tar.gz* for the latest version ( *2026c*) is *incorrect*. The content is *2026b* instead of *2026c*.
I'm not seeing that; see transcript below. Most likely this is related to the following text in the release announcement: "The following convenience links are also available, although they may point to the previous release until the relevant caches are refreshed".
Just confirming that we utilize Content Delivery Networks for publishing these assets, which can take time to propagate refreshed data when the URL doesn't change. While we send them instructions to invalidate their caches to retrieve the latest version each time we release a new version of the timezone database, it isn't instantaneous. While the -latest versions will necessarily have some minor lag in updating for this reason, the new releases with the version number embedded will always be up-to-date as their filename is novel. kim
On 7/8/26 13:30, Kim Davies via tz wrote:
... While the -latest versions will necessarily have some minor lag in updating for this reason, the new releases with the version number embedded will always be up-to-date as their filename is novel. ...
Can the If-Modified-Since and if-none-match request headers help to resolve this? But how many servers respect these? And how many clients even understand them? -- gil
Quoting Paul Gilmartin via tz on Wednesday July 08, 2026:
... While the -latest versions will necessarily have some minor lag in updating for this reason, the new releases with the version number embedded will always be up-to-date as their filename is novel. ...
Can the If-Modified-Since and if-none-match request headers help to resolve this?
I don't think so. The benefit of a CDN is to offload traffic from the origin servers by caching it for some period of time without rechecking if the content has changed. If the CDN nodes always checked back to the origin upon every request to check for freshness, it would defeat much of the purpose plus likely add intolerable latency. Yes, headers like If-Modified-Since would reduce the traffic, but it would still be blocking on a downstream call back to home.
But how many servers respect these? And how many clients even understand them?
I'd hope most modern HTTP implementations have this baked in! If you are a consumer of the -latest files, definitely use these headers when polling for updates to avoid unnecessarily pulling down the file when it hasn't changed. kim
Date: Wed, 8 Jul 2026 16:02:49 -0300 From: =?utf-8?q?Fabio_Brand=C3=A3o_via_tz?= <tz@iana.org> Message-ID: <CAHTJNv7ZQ3H300ooH1oWszCeGNWxi3ZU+54mhyXAQTXokNmrFw@mail.gmail.com> | The *version* file inside *tzdata-latest.tar.gz* for the latest version ( | *2026c*) is *incorrect*. The content is *2026b* instead of *2026c*. What makes you believe that? Check the leapseconds file, for me it has (near the end) #updated 1783323897 (2026-07-06 07:44:57 UTC) #expires 1814140800 (2027-06-28 00:00:00 UTC) That is, updated (almost) 3 days ago - 2026b was long before that. Similarly, the northamerica file has the updates for Alberta, and the africa file has updates for Morocco. What else were you expecting to see? kre ps: of course, I'm waiting for the gtz version to appear...
participants (6)
-
Fabio Brandão -
Kim Davies -
Paul Eggert -
Paul Eggert via tz-announce -
Paul Gilmartin -
Robert Elz