[tz] [tz-announce] 2026a release of tz code and data available

March 2, 2026

      The 2026a release of the tz code and data is available. This release 
corrects the time for Moldova's upcoming clock transition on March 29, 
as well as on other dates. It also has significant changes to code and 
to the build procedure.

This release contains the following changes:

   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.

   Changes to build procedure

     The Makefile no longer by default installs an alternate set
     of TZif files for system clocks that count leap seconds.
     Install with 'make REDO=posix_right' to get the old default,
     which is rarely used in major downstream distributions.
     If your system clock counts leap seconds (contrary to POSIX),
     it is better to install with 'make REDO=right_only'.
     This change does not affect the leapseconds file, which is still
     installed as before.

     The Makefile's POSIXRULES option, which was declared obsolete in
     release 2019b, has been removed.  The Makefile's build procedure
     thus no longer optionally installs the obsolete posixrules file.

   Changes to code

     Compiling with the new option -DTZ_RUNTIME_LEAPS=0 disables
     runtime support for leap seconds.  Although this conforms to
     POSIX, shrinks tzcode's attack surface, and is more efficient,
     it fails to support Internet RFC 9636's leap seconds.

     zic now can generate, and localtime.c can now use, TZif files that
     hold up to 256 bytes of abbreviations, counting trailing NULs.
     The previous limit was 50 bytes, and some tzdata TZif files were
     already consuming 40 bytes.  zic -v warns if it generates a file
     that exceeds the old 50-byte limit.

     zic -L can now generate TZif files with more than 50 leap seconds.
     This helps test TZif readers not limited to 50 leap seconds, as
     tzcode's localtime.c is; it has little immediate need for
     practical timekeeping as there have been only 27 leap seconds and
     possibly there will be no more, due to planned changes to UTC.
     zic -v warns if its output exceeds the old 50-second limit.

     localtime.c no longer accesses the posixrules file generated by
     zic -p.  Hence for obsolete and nonconforming settings like
     TZ="AST4ADT" it now typically falls back on US DST rules, rather
     than attempting to override this fallback with the contents of the
     posixrules file.  This removes library support that was declared
     obsolete in release 2019b, and fixes some undefined behavior.
     (Undefined behavior reported by GitHub user Naveed8951.)

     The posix2time, posix2time_z, time2posix, and time2posix_z
     functions now set errno=EOVERFLOW and return ((time_t) -1) if the
     result is not representable.  Formerly they had undefined behavior
     that could in practice result in crashing, looping indefinitely,
     or returning an incorrect result.  As before, these functions are
     defined only when localtime.c is compiled with the -DSTD_INSPIRED
     option.

     Some other undefined behavior, triggered by TZif files containing
     outlandish but conforming UT offsets or leap second corrections,
     has also been fixed.  (Some of these bugs reported by Naveed8951.)

     localtime.c no longer rejects TZif files that exactly fit in its
     internal structures, fixing off-by-one typos introduced in 2014g.

     zic no longer generates a no-op transition when
     simultaneous Rule and Zone changes cancel each other out.
     This occurs in tzdata only in Asia/Tbilisi on 1997-03-30.
     (Thanks to Renchunhui for a test case showing the bug.)

     zic no longer assumes you can fflush a read-only stream.
     (Problem reported by Christos Zoulas.)

     zic no longer generates UT offsets equal to -2**31 and localtime.c
     no longer accepts them, as they can cause trouble in both
     localtime.c and its callers.  RFC 9636 prohibits such offsets.

     zic -p now warns that the -p option is obsolete and likely
     ineffective.

Here are links to the release files:

   https://www.iana.org/time-zones/repository/releases/tzcode2026a.tar.gz
   https://www.iana.org/time-zones/repository/releases/tzdata2026a.tar.gz
   https://www.iana.org/time-zones/repository/releases/tzdb-2026a.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 
dd6be6d1558163517ec55c652efac70842c3b4cc dated 2026-03-01 22:59:49 -0800 
and tagged '2026a' in the development GitHub repository at 
<https://github.com/eggert/tz>.

Here are the SHA3-512 checksums for the release files, generated by
the GNU coreutils 9.8+ command 'cksum -a sha3 -l 512'.

SHA3-512 (tzcode2026a.tar.gz) = 
7106762916c6d21aa71fc5b43924582b603e231c90f19fb40ecd81db96208f8a4d6ff9664508c7298c521ab8fed97d4100665f84b2ba17caed04af129e40c5c2
SHA3-512 (tzdata2026a.tar.gz) = 
898b090b74d927495a412f382636e4eb2f697e3e357e5a1d35e01cf95f6cdc3bd52533a269ae247b521c6ec1112cbc2df0bb5466accf376e2e7b78a3adde26bd
SHA3-512 (tzdb-2026a.tar.lz) = 
5aefc96aa15113da1c30fbba7564636e106e3c0e33f475d48f32c5d3417e945fada548176e56c474a85bf02681e101c7b4dd727eb0053d1d39a81c9a13afe37b

Here are the SHA-512 checksums for the release files:

69a2ad3334ab1491ba349fcd5d3066a26b38ccb59031fec70ca19379cb0514fe2757af7bee31e796913c0cfc322134e2ba16f93ba07fa45cd4a415b9122b2f27 
  tzcode2026a.tar.gz
407e8e93aaa054a22a4a7d6d8cf480a20630073bf1a00956df16b10318f239a12015de38fad3072249193e314d6fddbff4e74afa40a88f7bf5c9eecc7659ea15 
  tzdata2026a.tar.gz
1824fc2e198a449ebaa41e6c679a494c486b848f13fe8f18f948fde0533e99f5f01e7e7298e257c565838d24ec743e824f402887abdf525d1ce578a714c71414 
  tzdb-2026a.tar.lz

Here are GPG digital signatures for the release files:

[tz] [tz-announce] 2026a release of tz code and data available

Paul Eggert via tz-announce