NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io · #748 most downloaded on crates.io
Create static TimeZone values for Jiff (useful in core-only environments).
Last release today
06 Oct 2026
Ships fairly regularly
a new release about every 3 weeks
Nearly every release is documented
notes for 37 of 37 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
37 releases · first in 2025
One column per month.
This release updates Jiff's bundled copy of the [IANA Time Zone Database] to 2026e. See the [2026e release announcement] for more details.
This release updates Jiff's bundled copy of the [IANA Time Zone Database]
to 2026e. See the 2026e release announcement for more details.
This is a redux release of 0.2.36 that fixes a compilation bug.
This is a redux release of 0.2.36 that fixes a compilation bug.
Bug fixes:
This release has a couple bug fixes and adds opt-in integration with the arbitrary crate.
This release has a couple bug fixes and adds opt-in integration with the
arbitrary crate.
Enhancements:
Arbitrary trait implementations from the arbitrary crate.Bug fixes:
This release fixes a bug in duration parsing where, e.g., -PT0.5S would be parsed as if the - sign didn't exist. This bug also affects friendly durati
This release fixes a bug in duration parsing where, e.g., -PT0.5S would be
parsed as if the - sign didn't exist. This bug also affects friendly
durations such as -0.5s.
Bug fixes:
This release contains a few small enhancements. Namely, some error messages for parsing datetime values have been improved by removing some redundant
This release contains a few small enhancements. Namely, some error messages
for parsing datetime values have been improved by removing some redundant
messaging. Additionally, the strftime APIs on datetime values can no longer
panic. Instead, they'll silently pass through invalid formatting directives.
Enhancements:
This release permits the use of a global time zone database in alloc-only environments. It also contains a massive internal refactor that introduces a
This release permits the use of a global time zone database in alloc-only
environments. It also contains a massive internal refactor that introduces a
new jiff-core crate for better code sharing.
Enhancements:
This release updates Jiff's bundled copy of the [IANA Time Zone Database] to 2026c. See the [2026c release announcement] for more details.
This release updates Jiff's bundled copy of the [IANA Time Zone Database]
to 2026c. See the 2026c release announcement for more details.
This release fixes a minor bug in tests that prevents the crate from running through standard build processes in Linux distributions downstream.
This release fixes a minor bug in tests that prevents the crate from running through standard build processes in Linux distributions downstream.
This release fixes a safety soundness bug in Jiff's lower level printing APIs. There is also a nice performance improvement to civil::Date::weekday, w
This release fixes a safety soundness bug in Jiff's lower level printing
APIs. There is also a nice performance improvement to civil::Date::weekday,
which also improves downstread routines like civil::Date::nth_weekday and
datetime<-->timestamp conversions in some cases.
Enhancements:
Bug fixes:
String destination buffer
with lower level printing APIs inside of jiff::fmt.This release adds support for [defmt], which is a highly efficient logging framework that targets resource-constrained devices, like microcontrollers.
This release adds support for [defmt], which is a highly efficient logging
framework that targets resource-constrained devices, like microcontrollers.
Enhancements:
defmt crate by implementing defmt::Format on the
principle public types in Jiff.Zoned::UNIX_EPOCH as a constant.Debug output for civil::ISOWeekDate to match the Debug output
style of other primitive datetime types.Bug fixes:
This is a small release with a fix for test failures on 32-bit targets in no-alloc environments.
This is a small release with a fix for test failures on 32-bit targets in
no-alloc environments.
Bug fixes:
no-alloc environments.This is a small release with a bug fix for build errors on Windows for very old versions of Rust.
This is a small release with a bug fix for build errors on Windows for very old versions of Rust.
Bug fixes:
This release has a couple enhancements.
This release has a couple enhancements.
Firstly, Jiff now uses windows-link for calling FFI routines on Windows
instead of windows-sys. Using windows-link means less churn and fewer
duplicates in the dependency graph.
Secondly, a new jiff-sqlx 0.2.0 release has been put out to support
sqlx 0.9.0.
Enhancements:
windows-sys with windows-link and inline bindings.jiff-sqlx to use sqlx 0.9.0 and release jiff-sqlx 0.2.0.Bug fixes:
RoundMode.This release updates Jiff's bundled copy of the [IANA Time Zone Database] to 2026b. See the [2026b release announcement] for more details.
This release updates Jiff's bundled copy of the [IANA Time Zone Database]
to 2026b. See the 2026b release announcement for more details.
This release primarily adds a new memory_usage routine for reporting heap allocation sizes for the TimeZone and Zoned types. This release also acknowl
This release primarily adds a new memory_usage routine for reporting
heap allocation sizes for the TimeZone and Zoned types. This
release also acknowledges and updates the timeline expectations for a
Jiff 1.0 release in README.md.
Enhancements:
memory_usage to the TimeZone and Zoned types.Span::checked_add example.Bug fixes:
This release updates Jiff's bundled copy of the [IANA Time Zone Database] to 2026a. See the [2026a release announcement] for more details.
This release updates Jiff's bundled copy of the [IANA Time Zone Database]
to 2026a. See the 2026a release announcement for more details.
This release includes a bug fix where fallible conversions from signed durations to unsigned durations could panic in some cases.
This release includes a bug fix where fallible conversions from signed durations to unsigned durations could panic in some cases.
Bug fixes:
std::time::Duration::try_from(SignedDuration::new(0, -1)).This release contains a performance improvement and a bug fix for civil::Date::new where it could panic on some inputs.
This release contains a performance improvement and a bug fix for
civil::Date::new where it could panic on some inputs.
Bug fixes:
Date::new could panic. This was a regression introduced in
jiff 0.2.20.Performance:
Timestamp to civil::DateTime conversion performance by ~15%.This release contains a major internal refactor that moves off of using ranged integers internally. There are also some small bug fixes and added supp
This release contains a major internal refactor that moves off of using ranged integers internally. There are also some small bug fixes and added support for finding the system time zone on emscripten targets.
Enhancements:
time crate in the Jiff documentation.Bug fixes:
This is a small release with a performance optimization (with respect to doing heavily contended arithmetic on Zoned values) and a bug fix for a panic
This is a small release with a performance optimization (with respect to doing
heavily contended arithmetic on Zoned values) and a bug fix for a panic
that can occur when using %2s in strftime.
Enhancements:
TimeZone for consuming operations on Zoned.Bug fixes:
timestamp.strftime("%2s").This release ships a sizeable refactor to the RFC 2822, RFC 9110, RC 3339, RFC 9557, ISO 8601 and friendly format printers. Specifically, they are now
This release ships a sizeable refactor to the RFC 2822, RFC 9110, RC
3339, RFC 9557, ISO 8601 and friendly format printers. Specifically,
they are now all monomorphic internally (instead of being generic over
jiff::fmt::Write) and write to uninitialized buffers. This improves
runtime performance (sometimes dramatically so), and to a more modest
degree, decreases binary size and improves compile times.
This release also includes a bug fix where DateTime::MIN.to_zoned(..)
could panic.
Enhancements:
jiff::SignedDuration.strftime
implementation.civil::DateTime::MIN could panic.(For example, some binary size improvements may require minor API breaking changes.)
This release contains binary size improvements to Jiff, more succinct error messages and some new minor APIs.
While Jiff 1.0 is overdue, I've been doing a lot of experimenting with improving Jiff's binary size and compile times. In particular, I want to spend time doing this before Jiff 1.0 so that we don't box ourselves into a corner. (For example, some binary size improvements may require minor API breaking changes.)
In this release, Jiff has switched to structured error handling internally in an effort to provide error predicates and also hopefully improve binary sizes and compile times. Overall this didn't have as big of an impact on binary sizes or compile times as I was hoping. I did take this opportunity to make Jiff's error messages a bit more succinct. In many cases, this involved de-duplicating some aspects of error messages and omitting user provided input in the messages. If you feel like there is a significant decrease in error message quality that isn't easily amended by callers providing additional context themselves, please open an issue.
This release also updates Jiff's bundled copy of the [IANA Time Zone Database]
to 2025c. See the 2025c release announcement for more details.
Enhancements:
Display, FromStr, Serialize and Deserialize trait implementations
for jiff::civil::ISOWeekDate. These all use the ISO 8601 week date format.jiff::Error for basic error introspection.This release contains a number of enhancements and bug fixes that have accrued over the last few months. Most are small polishes. A couple of the bug
This release contains a number of enhancements and bug fixes that have accrued
over the last few months. Most are small polishes. A couple of the bug fixes
apply to panics that could occur when parsing invalid TZ strings or invalid
strptime format strings.
Also, parsing into a Span should now be much faster (for both the ISO 8601
and "friendly" duration formats).
Enhancements:
std::time::Duration values.Sub and Add trait implementations for Zoned (in addition to the
already existing trait implementations for &Zoned).BrokenDownTime::set_meridiem and ensure it overrides the hour when
formatting.serde to serde_core. This should help speed up
compilation times in some cases.Zoned::series API, making it consistent with the same API on other
datetime types.lenient mode is enabled for strftime, Jiff will no longer error when
the formatting string contains invalid UTF-8.%y and %g no longer fails based on the specific year value.%s is now a bit more consistent with other fields. Moreover,
BrokenDownTime::{to_timestamp,to_zoned} will now prefer timestamps parsed
with %s over any other fields that have been parsed.%s into a Zoned via the Etc/Unknown time zone.Bug fixes:
2087-12-31T23:00:00Z in the Africa/Casablanca time zone
could not be round-tripped (because its offset was calculated incorrectly as
a result of not handling "permanent DST" POSIX time zones).%: via strptime APIs.TimeZone::unknown()
is a fallback for TimeZone::system() (instead of the jiff 0.1 behavior of
using TimeZone::UTC).%C) via strptime.-9223372036854775808s
and -PT9223372036854775808S.Performance:
Span or SignedDuration is now a fair bit faster in some cases.This release fixes a bug where error values were being constructed during parsing even in the success case. This was a regression introduced in 0.2.14
This release fixes a bug where error values were being constructed during
parsing even in the success case. This was a regression introduced in 0.2.14
as a result of trying to improve compilation times. Thankfully, fixing this
regression doesn't seem to meaningfully impact the amount of IR generated by
compiling Jiff.
Bug fixes:
This release includes a smattering of bug fixes, and hopefully a small improvement to the time it takes to compile Jiff. Also, in this release, when T
This release includes a smattering of bug fixes, and hopefully a small
improvement to the time it takes to compile Jiff. Also, in this release, when
TZ is set to a non-empty but invalid value, Jiff will always fall back to
Etc/Unknown when using TimeZone::system(). This differs from previous
behavior where Jiff would, in this case, attempt to read the system's default
time zone. This change brings Jiff into consistency with existing Unix tooling
like date, and is also arguably a better failure mode. That is, when TZ is
set but invalid, we shouldn't silently fall back to the default system time
zone, but instead do something that indicates something has potentially gone
wrong.
Enhancements:
Bug fixes:
This release fixes a bug in a corner case where TimeZone::following could sometimes omit the last time zone transition. This could only happen in time
This release fixes a bug in a corner case where TimeZone::following could
sometimes omit the last time zone transition. This could only happen in time
zones that once had daylight saving time, but ended it. This did not have an
impact on other Jiff APIs that handle daylight saving time.
Bug fixes:
TimeZone::following could omit the last historical time zone
transition.This release fixes a couple bugs in Jiff's parser. In particular, a regression was introduced in jiff 0.2.11 where its RFC 2822 parser could panic on
This release fixes a couple bugs in Jiff's parser. In particular, a regression
was introduced in jiff 0.2.11 where its RFC 2822 parser could panic on some
inputs. Previous releases of Jiff are unaffected.
Bug fixes:
This release includes new APIs for customizing Jiff's strtime behavior along with a few minor bug fixes. Jiff's strtime formatting API has also been o
This release includes new APIs for customizing Jiff's strtime behavior along
with a few minor bug fixes. Jiff's strtime formatting API has also been
optimized. It's about twice as fast as it was.
This release also coincides with the publication of jiff-icu 0.2.0-beta.2,
which has support for icu 2.0.0-beta.2.
Enhancements:
%c, %r, %X and %x conversion specifiers.%q in jiff::fmt::strtime (prints quarter of year).%::z and %:::z in jiff::fmt::strtime.%N in jiff::fmt::strtime (alias for %9f).strtime formatting APIs that ignores most errors.Bug fixes:
Display impls for datetime types.TimeZone::get("UTC") should now always return TimeZone::UTC.Performance:
strftime APIs are now approximately twice as fast as they were.
Performance should be comparable to chrono and time's prebuilt APIs.This release includes a bug fix for parsing Tuesday when using %A via Jiff's strptime APIs. Specifically, it would recognize Tueday instead of Tuesday
This release includes a bug fix for parsing Tuesday when using %A via
Jiff's strptime APIs. Specifically, it would recognize Tueday instead of
Tuesday.
Bug fixes:
strptime parsing from Tueday to Tuesday.This release includes a bug fix that, in debug mode, could result in datetime types having different hashes for the same value. This could cause probl
This release includes a bug fix that, in debug mode, could result in datetime types having different hashes for the same value. This could cause problems, for example, if you are using datetimes as keys in a hash map. This problem didn't exist when Jiff was compiled in release mode.
This release also improves the panic message shown when the js feature isn't
enabled and the current time is requested on wasm32-unknown-unknown targets.
Enhancements:
Zoned::now() fails on WASM.Bug fixes:
Hash on datetime types could yield different hash values for
the same underlying date/time.This release fixes a bug where the constructors on SignedDuration for floating point durations could panic (in debug mode) or produce incorrect result
This release fixes a bug where the constructors on SignedDuration
for floating point durations could panic (in debug mode) or produce
incorrect results (in release mode). This bug only impacts users of
the try_from_secs_{f32,f64} and from_secs_{f32,f64} methods on
SignedDuration.
Enhancements:
Debug impl for SignedDuration that only shows its second
and nanosecond components (while using only one component when the other is
zero).Bug fixes:
SignedDuration::(try_)?from_secs_{f32,f64}.This release includes a bug fix that changes how an empty but set TZ environment variable is interpreted (as indistinguishable from TZ=UTC). This also
This release includes a bug fix that changes how an empty but set TZ
environment variable is interpreted (as indistinguishable from TZ=UTC).
This also includes a new enabled by default create feature, perf-inline,
which allows toggling Jiff's use of inline(always). This may help improve
compile times or decrease binary size.
Enhancements:
perf-inline crate feature for controlling inline(always) annotations.Bug fixes:
TZ= indistinguishable from TZ=UTC.This release includes a few bug fixes and support for discovering the IANA Time Zone Database automatically on Illumos.
This release includes a few bug fixes and support for discovering the IANA Time Zone Database automatically on Illumos.
Enhancements:
Bug fixes:
This release updates Jiff's bundled copy of the [IANA Time Zone Database] to 2025b. See the [2025b release announcement] for more details.
This release updates Jiff's bundled copy of the [IANA Time Zone Database] to
2025b. See the 2025b release announcement for more details.
Enhancements:
jiff-tzdb to 2025b.This is another small release that fixes a problem where Jiff could break builds if they relied on inference for integer comparisons. Specifically, Ji
This is another small release that fixes a problem where Jiff could break builds if they relied on inference for integer comparisons. Specifically, Jiff uses internal trait impls to make comparing its internal ranged integers more convenient. But Rust the language has no concept of "internal" trait impls, and thus this can impact type inference. If code was written in a way that relies on a singular trait impl that is available, then adding Jiff to the project can cause it to break.
This isn't arguably Jiff's fault per se, but since these trait impls were just about internal convenience and not essential to Jiff's design, we adopt a pragmatic approach and just remove them.
Bug fixes:
This is a small release that fixes a bug in the handling of POSIX time zones in some cases. Specifically, the implementation of Date::yesterday was wr
This is a small release that fixes a bug in the handling of POSIX time zones
in some cases. Specifically, the implementation of Date::yesterday was wrong
when the date was the first of the month. This was a regression introduced in
0.2.2 and was not present in older releases. More test coverage has been
added.
Bug fixes:
Date::yesterday.This release of Jiff includes a new opt-in proc macro for embedding a TimeZone into your binary. Just enable Jiff's static feature, and this will prin
This release of Jiff includes a new opt-in proc macro for embedding a
TimeZone into your binary. Just enable Jiff's static feature, and this will
print the current time in the America/New_York time zone:
use jiff::{
tz::{self, TimeZone},
Timestamp,
};
fn main() {
static TZ: TimeZone = tz::get!("America/New_York");
let zdt = Timestamp::now().to_zoned(TZ.clone());
println!("{zdt}");
}
This enables TimeZone to be meaningfully used in core-only environments,
even when dynamic memory allocation isn't available.
This release also features a number of performance improvements for time zone lookups. In some cases, the improvement is significant (by an order of magnitude).
Additionally, the IANA Time Zone Database embedded into jiff-tzdb now
uses "rearguard" semantics. This means that the boolean flag indicating
whether daylight saving time is active or not (only accessible via
TimeZone::to_offset_info) will respect the actual definition of
daylight saving time. (This is relevant, for example, for time zones like
Europe/Dublin, where their summer time is legally known as their standard
time, but is in effect daylight saving time.)
Enhancements:
tz::{get,include} macros for time zone support in core-only environments.rearguard tzdb data in jiff-tzdb and document it.jiff-tzdb.jiff-sqlx and jiff-diesel.Timestamp constructors.Bug fixes:
ZonedWith::nanosecond and
ZonedWith::subsec_nanosecond.Your coding agent can read these notes before it upgrades. Set up the MCP server →