5 curated breaking changes across major versions of jiff-tzdb-platform. Use this as a migration checklist before bumping dependencies.
[#28](https://github.com/BurntSushi/jiff/issues/28): The deprecated `intz` routines on `Zoned`, `Timestamp`, `civil::DateTime` and `civil::Date` have been removed. You can use `in_tz` instead. This change was made because many found the name `intz` to be unclear.
[#32](https://github.com/BurntSushi/jiff/issues/32): The `PartialEq` and `Eq` trait implementations on `Span` have been removed. Ideally these shouldn't have been used, but if you do need them, please use `Span::fieldwise` to create a `SpanFieldwise`, which does have the `PartialEq` and `Eq` traits implemented. These were removed on `Span` itself because they made it very easy to commit subtle bugs.
[#36](https://github.com/BurntSushi/jiff/issues/36): Turn panics during `Timestamp::saturing_add` into errors. Callers adding spans that are known to contain units of hours or smaller are guaranteed that this will not return an error.
Get this data programmatically \u2014 free, no authentication.
curl https://depscope.dev/api/breaking/cargo/jiff-tzdb-platform**RUNTIME** [#48](https://github.com/BurntSushi/jiff/issues/48): On `Span` APIs, days are no longer silently assumed to always be 24 hours when a relative datetime is not provided. Instead, to perform operations on units of days or bigger, callers must either provide a relative date or opt into invariant 24-hour days with `SpanRelativeTo::days_are_24_hours`. Shortcuts have been added to the span builders. For example, `SpanTotal::days_are_24_hours`.
**RUNTIME** [#147](https://github.com/BurntSushi/jiff/issues/147): Change the behavior of the deprecated `%V` conversion specifier in `jiff::fmt::strtime` from formatting an IANA time zone identifier to formatting an ISO 8601 week number. To format an IANA time zone identifier, use `%Q` or `%:Q` (which were introduced in `jiff 0.1`).