Jiff 1.0 released: Rust's time zone-aware datetime library goes stable
Andrew Gallant (BurntSushi), the author of ripgrep, released Jiff 1.0 on November 15, 2026, the first stable version of his datetime library for Rust. Jiff already runs in production in uv, Cargo, Starship, fd, Nushell, mise, Jujutsu and uutils/coreutils, and the 1.0 release comes with a promise that there will be no 2.0 “unless some significant defect is found” in its API. For Rust developers, that makes Jiff types safe to put in the public API of their own crates.
What’s new
Jiff 1.0.0 was published to crates.io on November 15, a couple of hours after the last 0.2 release, 0.2.46. In the announcement post, Gallant says he plans to commit to Jiff 1.0 indefinitely, because the crate is meant to be “an ecosystem building block” that other libraries expose, and a semver-incompatible release would cause significant pain.
The changelog lists the breaking changes from 0.2:
Zonedis nowZonedDateTime, the biggest change. Methods named after it follow, soTimestamp::to_zonedbecomesTimestamp::to_zoned_datetime.- Subtracting two
Timestampvalues with-now returns aSignedDuration. - Conversions from
TimestamptoSystemTimeare now fallible, and so isOffset::saturating_add. - The
ToSpantrait is sealed, andZoned::iso_week_date(now onZonedDateTime) takes&selfinstead ofself. jiff_tzdb::VERSIONis required.
Other changes: the minimum supported Rust version rises to Rust 1.85 (0.2.46 required 1.70), errors use core::error::Error instead of std::error::Error, more methods take &self, and a new Span::to_friendly method prints a span in Jiff’s readable duration format, such as 3mo 23d 20h. The 0.2.44 release a few days earlier updated Jiff’s bundled IANA Time Zone Database to tzdb 2026f.
What Jiff does
Jiff’s main idea is to put time zones at the front of the API so that daylight saving time bugs are hard to write. Its core types build on each other: civil::Date, civil::Time and civil::DateTime are plain clock values with no location, a Timestamp is an exact instant in nanoseconds since the Unix epoch, a TimeZone maps between the two, and a ZonedDateTime holds all three.
When a local time is ambiguous, such as 1:30 AM on the night clocks go back, Jiff picks the first occurrence by default (its “compatible” strategy) and lets you choose earlier(), later() or an error instead. Its Span type mixes calendar units (years, months, days) with clock units, and can be rounded and compared relative to a specific date, because the length of a month depends on which month it is.
For strings, Jiff reads and writes RFC 3339 (2026-11-12T15:36:00-05:00), RFC 9557 with a time zone name (2026-11-12T15:36:00-05:00[America/New_York]) and ISO 8601 durations, plus strftime/strptime. Locale-aware formatting is left to the ICU4X project through the separate jiff-icu crate, and Jiff itself only supports the Gregorian calendar, with a range of years from -9999 to 9999.
What it means for developers
To try it in a new project:
cargo add jiff
For a project on Jiff 0.2, the upgrade is mostly a search and replace of Zoned with ZonedDateTime, then fixing any code that subtracts timestamps or converts them to SystemTime. Your toolchain needs to be Rust 1.85 or newer. Library authors can now expose Jiff types in their own public APIs with the 1.x stability promise behind them.
Gallant’s own advice is that you don’t always need Jiff: to measure how long something takes, use the standard library’s monotonic std::time::Instant, and if you live entirely in UTC with Unix timestamps, std::time::SystemTime is enough. Jiff earns its place once you deal with local time, time zones, calendar math or formats like RFC 3339.
How it compares
Rust’s two established datetime crates are chrono and time. Gallant writes that he found their APIs confusing and that both had “reached a local maximum” by 2024, so he wrote Jiff rather than push either in a different direction; the project’s design and comparison docs go into detail. Jiff is heavily inspired by Temporal, JavaScript’s standard date and time API, though it doesn’t aim to be fully compatible: Temporal’s Duration is Span in Jiff, Instant is Timestamp, and the “plain” types are called “civil”.
JavaScript developers have their own long-running choice between date libraries; see our Day.js vs Moment.js comparison. For another library that just promised a stable API, see libghostty 1.0.
Sources
- Jiff: A datetime library for Rust (Andrew Gallant’s blog)
- Jiff CHANGELOG (GitHub)
- jiff on crates.io