Add history of chrono and time 0.1 to main documentation #1264

pitdicker · 2023-09-07T10:11:47Z

Split out from #1246.

djc · 2023-09-07T10:17:30Z

I'll approve this, please merge it, then I will do some editing.

pitdicker · 2023-09-07T10:18:36Z

That is the best way for documentation in my opinion.

codecov · 2023-09-07T10:19:03Z

Codecov Report

Merging #1264 (a83ff4a) into 0.4.x (8509da4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            0.4.x    #1264   +/-   ##
=======================================
  Coverage   91.40%   91.40%           
=======================================
  Files          38       38           
  Lines       16933    16933           
=======================================
  Hits        15478    15478           
  Misses       1455     1455

Files Changed	Coverage Δ
src/lib.rs	`95.58% <ø> (ø)`

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [chrono](https://togithub.com/chronotope/chrono) | dependencies | patch | `0.4.29` -> `0.4.30` | --- ### Release Notes <details> <summary>chronotope/chrono (chrono)</summary> ### [`v0.4.30`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.30): 0.4.30 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.29...v0.4.30) In this release, we have decided to swap out the `chrono::Duration` type (which has been a re-export of time 0.1 `Duration` type) with our own definition, which exposes a strict superset of the `time::Duration` API. This helps avoid warnings about the [CVE-2020-26235] and [RUSTSEC-2020-0071] advisories for downstream users and allows us to improve the `Duration` API going forward. While this is technically a SemVer-breaking change, we expect the risk of downstream users experiencing actual incompatibility to be exceedingly limited (see [our analysis](https://togithub.com/chronotope/chrono/pull/1095#issuecomment-1571716955) of public code using a crater-like experiment), and not enough justification for the large ecosystem churn of a 0.5 release. If you have any feedback on these changes, please let us know in [#1268](https://togithub.com/chronotope/chrono/issues/1268). ##### Additions - Add `NaiveDate::leap_year` ([#1261](https://togithub.com/chronotope/chrono/issues/1261)) ##### Documentation - Update main documentation from README ([#1260](https://togithub.com/chronotope/chrono/issues/1260), thanks [@Stygmates](https://togithub.com/Stygmates)) - Add history of relation between chrono and time 0.1 to documentation ([https://github.com/chronotope/chrono/pull/1264](https://togithub.com/chronotope/chrono/pull/1264), [https://github.com/chronotope/chrono/pull/1266](https://togithub.com/chronotope/chrono/pull/1266)) - Clarify `Timelike::num_seconds_from_midnight` is a simple mapping ([#1255](https://togithub.com/chronotope/chrono/issues/1255)) #### Relation between chrono and time 0.1 Rust first had a `time` module added to `std` in its 0.7 release. It later moved to `libextra`, and then to a `libtime` library shipped alongside the standard library. In 2014 work on chrono started in order to provide a full-featured date and time library in Rust. Some improvements from chrono made it into the standard library; notably, `chrono::Duration` was included as `std::time::Duration` ([rust#15934]) in 2014. In preparation of Rust 1.0 at the end of 2014 `libtime` was moved out of the Rust distro and into the `time` crate to eventually be redesigned ([rust#18832], [rust#18858]), like the `num` and `rand` crates. Of course chrono kept its dependency on this `time` crate. `time` started re-exporting `std::time::Duration` during this period. Later, the standard library was changed to have a more limited unsigned `Duration` type ([rust#24920], [RFC 1040]), while the `time` crate kept the full functionality with `time::Duration`. `time::Duration` had been a part of chrono's public API. By 2016 `time` 0.1 lived under the `rust-lang-deprecated` organisation and was not actively maintained ([time#136]). chrono absorbed the platform functionality and `Duration` type of the `time` crate in [chrono#478] (the work started in [chrono#286]). In order to preserve compatibility with downstream crates depending on `time` and `chrono` sharing a `Duration` type, chrono kept depending on time 0.1. chrono offered the option to opt out of the `time` dependency by disabling the `oldtime` feature (swapping it out for an effectively similar chrono type). In 2019, [@jhpratt](https://togithub.com/jhpratt) took over maintenance on the `time` crate and released what amounts to a new crate as `time` 0.2. [rust#15934]: https://togithub.com/rust-lang/rust/pull/15934 [rust#18832]: https://togithub.com/rust-lang/rust/pull/18832#issuecomment-62448221 [rust#18858]: https://togithub.com/rust-lang/rust/pull/18858 [rust#24920]: https://togithub.com/rust-lang/rust/pull/24920 [RFC 1040]: https://rust-lang.github.io/rfcs/1040-duration-reform.html [time#136]: https://togithub.com/time-rs/time/issues/136 [chrono#286]: https://togithub.com/chronotope/chrono/pull/286 [chrono#478]: https://togithub.com/chronotope/chrono/pull/478 ##### Security advisories In November of 2020 [CVE-2020-26235] and [RUSTSEC-2020-0071] were opened against the `time` crate. [@quininer](https://togithub.com/quininer) had found that calls to `localtime_r` may be unsound ([chrono#499]). Eventually, almost a year later, this was also made into a security advisory against chrono as [RUSTSEC-2020-0159], which had platform code similar to `time`. On Unix-like systems a process is given a timezone id or description via the `TZ` environment variable. We need this timezone data to calculate the current local time from a value that is in UTC, such as the time from the system clock. `time` 0.1 and chrono used the POSIX function `localtime_r` to do the conversion to local time, which reads the `TZ` variable. Rust assumes the environment to be writable and uses locks to access it from multiple threads. Some other programming languages and libraries use similar locking strategies, but these are typically not shared across languages. More importantly, POSIX declares modifying the environment in a multi-threaded process as unsafe, and `getenv` in libc can't be changed to take a lock because it returns a pointer to the data (see [rust#27970] for more discussion). Since version 4.20 chrono no longer uses `localtime_r`, instead using Rust code to query the timezone (from the `TZ` variable or via `iana-time-zone` as a fallback) and work with data from the system timezone database directly. The code for this was forked from the [tz-rs crate] by [@x-hgg-x](https://togithub.com/x-hgg-x). As such, chrono now respects the Rust lock when reading the `TZ` environment variable. In general, code should avoid modifying the environment. [CVE-2020-26235]: https://nvd.nist.gov/vuln/detail/CVE-2020-26235 [RUSTSEC-2020-0071]: https://rustsec.org/advisories/RUSTSEC-2020-0071 [chrono#499]: https://togithub.com/chronotope/chrono/pull/499 [RUSTSEC-2020-0159]: https://rustsec.org/advisories/RUSTSEC-2020-0159.html [rust#27970]: https://togithub.com/rust-lang/rust/issues/27970 [chrono#677]: https://togithub.com/chronotope/chrono/pull/677 [tz-rs crate]: https://crates.io/crates/tz-rs ##### Removing time 0.1 Because time 0.1 has been unmaintained for years, however, the security advisory mentioned above has not been addressed. While chrono maintainers were careful not to break backwards compatibility with the `time::Duration` type, there has been a long stream of issues from users inquiring about the time 0.1 dependency with the vulnerability. We investigated the potential breakage of removing the time 0.1 dependency in [chrono#1095] using a crater-like experiment and determined that the potential for breaking (public) dependencies is very low. We reached out to those few crates that did still depend on compatibility with time 0.1. As such, for chrono 0.4.30 we have decided to swap out the time 0.1 `Duration` implementation for a local one that will offer a strict superset of the existing API going forward. This will prevent most downstream users from being affected by the security vulnerability in time 0.1 while minimizing the ecosystem impact of semver-incompatible version churn. [chrono#1095]: https://togithub.com/chronotope/chrono/pull/1095 Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/ziyadedher/evm-bench).  Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [chrono](https://togithub.com/chronotope/chrono) | dependencies | patch | `0.4.28` -> `0.4.30` | --- ### Release Notes <details> <summary>chronotope/chrono (chrono)</summary> ### [`v0.4.30`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.30): 0.4.30 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.29...v0.4.30) In this release, we have decided to swap out the `chrono::Duration` type (which has been a re-export of time 0.1 `Duration` type) with our own definition, which exposes a strict superset of the `time::Duration` API. This helps avoid warnings about the [CVE-2020-26235] and [RUSTSEC-2020-0071] advisories for downstream users and allows us to improve the `Duration` API going forward. While this is technically a SemVer-breaking change, we expect the risk of downstream users experiencing actual incompatibility to be exceedingly limited (see [our analysis](https://togithub.com/chronotope/chrono/pull/1095#issuecomment-1571716955) of public code using a crater-like experiment), and not enough justification for the large ecosystem churn of a 0.5 release. If you have any feedback on these changes, please let us know in [#1268](https://togithub.com/chronotope/chrono/issues/1268). ##### Additions - Add `NaiveDate::leap_year` ([#1261](https://togithub.com/chronotope/chrono/issues/1261)) ##### Documentation - Update main documentation from README ([#1260](https://togithub.com/chronotope/chrono/issues/1260), thanks [@Stygmates](https://togithub.com/Stygmates)) - Add history of relation between chrono and time 0.1 to documentation ([https://github.com/chronotope/chrono/pull/1264](https://togithub.com/chronotope/chrono/pull/1264), [https://github.com/chronotope/chrono/pull/1266](https://togithub.com/chronotope/chrono/pull/1266)) - Clarify `Timelike::num_seconds_from_midnight` is a simple mapping ([#1255](https://togithub.com/chronotope/chrono/issues/1255)) #### Relation between chrono and time 0.1 Rust first had a `time` module added to `std` in its 0.7 release. It later moved to `libextra`, and then to a `libtime` library shipped alongside the standard library. In 2014 work on chrono started in order to provide a full-featured date and time library in Rust. Some improvements from chrono made it into the standard library; notably, `chrono::Duration` was included as `std::time::Duration` ([rust#15934]) in 2014. In preparation of Rust 1.0 at the end of 2014 `libtime` was moved out of the Rust distro and into the `time` crate to eventually be redesigned ([rust#18832], [rust#18858]), like the `num` and `rand` crates. Of course chrono kept its dependency on this `time` crate. `time` started re-exporting `std::time::Duration` during this period. Later, the standard library was changed to have a more limited unsigned `Duration` type ([rust#24920], [RFC 1040]), while the `time` crate kept the full functionality with `time::Duration`. `time::Duration` had been a part of chrono's public API. By 2016 `time` 0.1 lived under the `rust-lang-deprecated` organisation and was not actively maintained ([time#136]). chrono absorbed the platform functionality and `Duration` type of the `time` crate in [chrono#478] (the work started in [chrono#286]). In order to preserve compatibility with downstream crates depending on `time` and `chrono` sharing a `Duration` type, chrono kept depending on time 0.1. chrono offered the option to opt out of the `time` dependency by disabling the `oldtime` feature (swapping it out for an effectively similar chrono type). In 2019, [@jhpratt](https://togithub.com/jhpratt) took over maintenance on the `time` crate and released what amounts to a new crate as `time` 0.2. [rust#15934]: https://togithub.com/rust-lang/rust/pull/15934 [rust#18832]: https://togithub.com/rust-lang/rust/pull/18832#issuecomment-62448221 [rust#18858]: https://togithub.com/rust-lang/rust/pull/18858 [rust#24920]: https://togithub.com/rust-lang/rust/pull/24920 [RFC 1040]: https://rust-lang.github.io/rfcs/1040-duration-reform.html [time#136]: https://togithub.com/time-rs/time/issues/136 [chrono#286]: https://togithub.com/chronotope/chrono/pull/286 [chrono#478]: https://togithub.com/chronotope/chrono/pull/478 ##### Security advisories In November of 2020 [CVE-2020-26235] and [RUSTSEC-2020-0071] were opened against the `time` crate. [@quininer](https://togithub.com/quininer) had found that calls to `localtime_r` may be unsound ([chrono#499]). Eventually, almost a year later, this was also made into a security advisory against chrono as [RUSTSEC-2020-0159], which had platform code similar to `time`. On Unix-like systems a process is given a timezone id or description via the `TZ` environment variable. We need this timezone data to calculate the current local time from a value that is in UTC, such as the time from the system clock. `time` 0.1 and chrono used the POSIX function `localtime_r` to do the conversion to local time, which reads the `TZ` variable. Rust assumes the environment to be writable and uses locks to access it from multiple threads. Some other programming languages and libraries use similar locking strategies, but these are typically not shared across languages. More importantly, POSIX declares modifying the environment in a multi-threaded process as unsafe, and `getenv` in libc can't be changed to take a lock because it returns a pointer to the data (see [rust#27970] for more discussion). Since version 4.20 chrono no longer uses `localtime_r`, instead using Rust code to query the timezone (from the `TZ` variable or via `iana-time-zone` as a fallback) and work with data from the system timezone database directly. The code for this was forked from the [tz-rs crate] by [@x-hgg-x](https://togithub.com/x-hgg-x). As such, chrono now respects the Rust lock when reading the `TZ` environment variable. In general, code should avoid modifying the environment. [CVE-2020-26235]: https://nvd.nist.gov/vuln/detail/CVE-2020-26235 [RUSTSEC-2020-0071]: https://rustsec.org/advisories/RUSTSEC-2020-0071 [chrono#499]: https://togithub.com/chronotope/chrono/pull/499 [RUSTSEC-2020-0159]: https://rustsec.org/advisories/RUSTSEC-2020-0159.html [rust#27970]: https://togithub.com/rust-lang/rust/issues/27970 [chrono#677]: https://togithub.com/chronotope/chrono/pull/677 [tz-rs crate]: https://crates.io/crates/tz-rs ##### Removing time 0.1 Because time 0.1 has been unmaintained for years, however, the security advisory mentioned above has not been addressed. While chrono maintainers were careful not to break backwards compatibility with the `time::Duration` type, there has been a long stream of issues from users inquiring about the time 0.1 dependency with the vulnerability. We investigated the potential breakage of removing the time 0.1 dependency in [chrono#1095] using a crater-like experiment and determined that the potential for breaking (public) dependencies is very low. We reached out to those few crates that did still depend on compatibility with time 0.1. As such, for chrono 0.4.30 we have decided to swap out the time 0.1 `Duration` implementation for a local one that will offer a strict superset of the existing API going forward. This will prevent most downstream users from being affected by the security vulnerability in time 0.1 while minimizing the ecosystem impact of semver-incompatible version churn. [chrono#1095]: https://togithub.com/chronotope/chrono/pull/1095 Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.29`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.29): 0.4.29 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.28...v0.4.29) This release fixes a panic introduced in chrono 0.4.27 in `FromStr<DateTime<Utc>>` ([#1253](https://togithub.com/chronotope/chrono/issues/1253)). Chrono now has a [Discord channel](https://discord.gg/sXpav4PS7M). #### Fixes - Fix arbitrary string slicing in `parse_rfc3339_relaxed` ([#1254](https://togithub.com/chronotope/chrono/issues/1254)) #### Deprecations - Deprecate `TimeZone::datetime_from_str` ([#1251](https://togithub.com/chronotope/chrono/issues/1251)) #### Documentation - Correct documentation for `FromStr` for `Weekday` and `Month` ([#1226](https://togithub.com/chronotope/chrono/issues/1226), thanks [@wfraser](https://togithub.com/wfraser)) #### Internal improvements - Revert "add test_issue\_866" ([#1238](https://togithub.com/chronotope/chrono/issues/1238)) - CI: run tests on `i686` and `wasm32-wasi` ([#1237](https://togithub.com/chronotope/chrono/issues/1237)) - CI: Include doctests for code coverage ([#1248](https://togithub.com/chronotope/chrono/issues/1248)) - Move benchmarks to a separate crate ([#1243](https://togithub.com/chronotope/chrono/issues/1243)) This allows us to upgrade the criterion dependency to 5.1 without changing our MSRV. - Add Discord link to README ([#1240](https://togithub.com/chronotope/chrono/issues/1240), backported in [#1256](https://togithub.com/chronotope/chrono/issues/1256)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/grafbase/grafbase).

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [chrono](https://togithub.com/chronotope/chrono) | workspace.dependencies | patch | `0.4.23` -> `0.4.31` | --- ### Release Notes <details> <summary>chronotope/chrono (chrono)</summary> ### [`v0.4.31`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.31): 0.4.31 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.30...v0.4.31) Another maintenance release. It was not a planned effort to improve our support for UNIX timestamps, yet most PRs seem related to this. ##### Deprecations - Deprecate `timestamp_nanos` in favor of the non-panicking `timestamp_nanos_opt` ([#1275](https://togithub.com/chronotope/chrono/issues/1275)) ##### Additions - Add `DateTime::<Utc>::from_timestamp` ([#1279](https://togithub.com/chronotope/chrono/issues/1279), thanks [@demurgos](https://togithub.com/demurgos)) - Add `TimeZone::timestamp_micros` ([#1285](https://togithub.com/chronotope/chrono/issues/1285), thanks [@emikitas](https://togithub.com/emikitas)) - Add `DateTime<Tz>::timestamp_nanos_opt` and `NaiveDateTime::timestamp_nanos_opt` ([#1275](https://togithub.com/chronotope/chrono/issues/1275)) - Add `UNIX_EPOCH` constants ([#1291](https://togithub.com/chronotope/chrono/issues/1291)) ##### Fixes - Format day of month in RFC 2822 without padding ([#1272](https://togithub.com/chronotope/chrono/issues/1272)) - Don't allow strange leap seconds which are not on a minute boundary initialization methods ([#1283](https://togithub.com/chronotope/chrono/issues/1283)) This makes many methods a little more strict: - `NaiveTime::from_hms_milli` - `NaiveTime::from_hms_milli_opt` - `NaiveTime::from_hms_micro` - `NaiveTime::from_hms_micro_opt` - `NaiveTime::from_hms_nano` - `NaiveTime::from_hms_nano_opt` - `NaiveTime::from_num_seconds_from_midnight` - `NaiveTime::from_num_seconds_from_midnight_opt` - `NaiveDate::and_hms_milli` - `NaiveDate::and_hms_milli_opt` - `NaiveDate::and_hms_micro` - `NaiveDate::and_hms_micro_opt` - `NaiveDate::and_hms_nano` - `NaiveDate::and_hms_nano_opt` - `NaiveDateTime::from_timestamp` - `NaiveDateTime::from_timestamp_opt` - `TimeZone::timestamp` - `TimeZone::timestamp_opt` - Fix underflow in `NaiveDateTime::timestamp_nanos_opt` ([#1294](https://togithub.com/chronotope/chrono/issues/1294), thanks [@crepererum](https://togithub.com/crepererum)) ##### Documentation - Add more documentation about the RFC 2822 obsolete date format ([#1267](https://togithub.com/chronotope/chrono/issues/1267)) ##### Internal - Remove internal `__doctest` feature and `doc_comment` dependency ([#1276](https://togithub.com/chronotope/chrono/issues/1276)) - CI: Bump `actions/checkout` from 3 to 4 ([#1280](https://togithub.com/chronotope/chrono/issues/1280)) - Optimize `NaiveDate::add_days` for small values ([#1214](https://togithub.com/chronotope/chrono/issues/1214)) - Upgrade `pure-rust-locales` to 0.7.0 ([#1288](https://togithub.com/chronotope/chrono/issues/1288), thanks [@jeremija](https://togithub.com/jeremija) wo did good improvements on `pure-rust-locales`) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.30`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.30): 0.4.30 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.29...v0.4.30) In this release, we have decided to swap out the `chrono::Duration` type (which has been a re-export of time 0.1 `Duration` type) with our own definition, which exposes a strict superset of the `time::Duration` API. This helps avoid warnings about the [CVE-2020-26235] and [RUSTSEC-2020-0071] advisories for downstream users and allows us to improve the `Duration` API going forward. While this is technically a SemVer-breaking change, we expect the risk of downstream users experiencing actual incompatibility to be exceedingly limited (see [our analysis](https://togithub.com/chronotope/chrono/pull/1095#issuecomment-1571716955) of public code using a crater-like experiment), and not enough justification for the large ecosystem churn of a 0.5 release. If you have any feedback on these changes, please let us know in [#1268](https://togithub.com/chronotope/chrono/issues/1268). ##### Additions - Add `NaiveDate::leap_year` ([#1261](https://togithub.com/chronotope/chrono/issues/1261)) ##### Documentation - Update main documentation from README ([#1260](https://togithub.com/chronotope/chrono/issues/1260), thanks [@Stygmates](https://togithub.com/Stygmates)) - Add history of relation between chrono and time 0.1 to documentation ([https://github.com/chronotope/chrono/pull/1264](https://togithub.com/chronotope/chrono/pull/1264), [https://github.com/chronotope/chrono/pull/1266](https://togithub.com/chronotope/chrono/pull/1266)) - Clarify `Timelike::num_seconds_from_midnight` is a simple mapping ([#1255](https://togithub.com/chronotope/chrono/issues/1255)) #### Relation between chrono and time 0.1 Rust first had a `time` module added to `std` in its 0.7 release. It later moved to `libextra`, and then to a `libtime` library shipped alongside the standard library. In 2014 work on chrono started in order to provide a full-featured date and time library in Rust. Some improvements from chrono made it into the standard library; notably, `chrono::Duration` was included as `std::time::Duration` ([rust#15934]) in 2014. In preparation of Rust 1.0 at the end of 2014 `libtime` was moved out of the Rust distro and into the `time` crate to eventually be redesigned ([rust#18832], [rust#18858]), like the `num` and `rand` crates. Of course chrono kept its dependency on this `time` crate. `time` started re-exporting `std::time::Duration` during this period. Later, the standard library was changed to have a more limited unsigned `Duration` type ([rust#24920], [RFC 1040]), while the `time` crate kept the full functionality with `time::Duration`. `time::Duration` had been a part of chrono's public API. By 2016 `time` 0.1 lived under the `rust-lang-deprecated` organisation and was not actively maintained ([time#136]). chrono absorbed the platform functionality and `Duration` type of the `time` crate in [chrono#478] (the work started in [chrono#286]). In order to preserve compatibility with downstream crates depending on `time` and `chrono` sharing a `Duration` type, chrono kept depending on time 0.1. chrono offered the option to opt out of the `time` dependency by disabling the `oldtime` feature (swapping it out for an effectively similar chrono type). In 2019, [@jhpratt](https://togithub.com/jhpratt) took over maintenance on the `time` crate and released what amounts to a new crate as `time` 0.2. [rust#15934]: https://togithub.com/rust-lang/rust/pull/15934 [rust#18832]: https://togithub.com/rust-lang/rust/pull/18832#issuecomment-62448221 [rust#18858]: https://togithub.com/rust-lang/rust/pull/18858 [rust#24920]: https://togithub.com/rust-lang/rust/pull/24920 [RFC 1040]: https://rust-lang.github.io/rfcs/1040-duration-reform.html [time#136]: https://togithub.com/time-rs/time/issues/136 [chrono#286]: https://togithub.com/chronotope/chrono/pull/286 [chrono#478]: https://togithub.com/chronotope/chrono/pull/478 ##### Security advisories In November of 2020 [CVE-2020-26235] and [RUSTSEC-2020-0071] were opened against the `time` crate. [@quininer](https://togithub.com/quininer) had found that calls to `localtime_r` may be unsound ([chrono#499]). Eventually, almost a year later, this was also made into a security advisory against chrono as [RUSTSEC-2020-0159], which had platform code similar to `time`. On Unix-like systems a process is given a timezone id or description via the `TZ` environment variable. We need this timezone data to calculate the current local time from a value that is in UTC, such as the time from the system clock. `time` 0.1 and chrono used the POSIX function `localtime_r` to do the conversion to local time, which reads the `TZ` variable. Rust assumes the environment to be writable and uses locks to access it from multiple threads. Some other programming languages and libraries use similar locking strategies, but these are typically not shared across languages. More importantly, POSIX declares modifying the environment in a multi-threaded process as unsafe, and `getenv` in libc can't be changed to take a lock because it returns a pointer to the data (see [rust#27970] for more discussion). Since version 4.20 chrono no longer uses `localtime_r`, instead using Rust code to query the timezone (from the `TZ` variable or via `iana-time-zone` as a fallback) and work with data from the system timezone database directly. The code for this was forked from the [tz-rs crate] by [@x-hgg-x](https://togithub.com/x-hgg-x). As such, chrono now respects the Rust lock when reading the `TZ` environment variable. In general, code should avoid modifying the environment. [CVE-2020-26235]: https://nvd.nist.gov/vuln/detail/CVE-2020-26235 [RUSTSEC-2020-0071]: https://rustsec.org/advisories/RUSTSEC-2020-0071 [chrono#499]: https://togithub.com/chronotope/chrono/pull/499 [RUSTSEC-2020-0159]: https://rustsec.org/advisories/RUSTSEC-2020-0159.html [rust#27970]: https://togithub.com/rust-lang/rust/issues/27970 [chrono#677]: https://togithub.com/chronotope/chrono/pull/677 [tz-rs crate]: https://crates.io/crates/tz-rs ##### Removing time 0.1 Because time 0.1 has been unmaintained for years, however, the security advisory mentioned above has not been addressed. While chrono maintainers were careful not to break backwards compatibility with the `time::Duration` type, there has been a long stream of issues from users inquiring about the time 0.1 dependency with the vulnerability. We investigated the potential breakage of removing the time 0.1 dependency in [chrono#1095] using a crater-like experiment and determined that the potential for breaking (public) dependencies is very low. We reached out to those few crates that did still depend on compatibility with time 0.1. As such, for chrono 0.4.30 we have decided to swap out the time 0.1 `Duration` implementation for a local one that will offer a strict superset of the existing API going forward. This will prevent most downstream users from being affected by the security vulnerability in time 0.1 while minimizing the ecosystem impact of semver-incompatible version churn. [chrono#1095]: https://togithub.com/chronotope/chrono/pull/1095 Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.29`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.29): 0.4.29 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.28...v0.4.29) This release fixes a panic introduced in chrono 0.4.27 in `FromStr<DateTime<Utc>>` ([#1253](https://togithub.com/chronotope/chrono/issues/1253)). Chrono now has a [Discord channel](https://discord.gg/sXpav4PS7M). #### Fixes - Fix arbitrary string slicing in `parse_rfc3339_relaxed` ([#1254](https://togithub.com/chronotope/chrono/issues/1254)) #### Deprecations - Deprecate `TimeZone::datetime_from_str` ([#1251](https://togithub.com/chronotope/chrono/issues/1251)) #### Documentation - Correct documentation for `FromStr` for `Weekday` and `Month` ([#1226](https://togithub.com/chronotope/chrono/issues/1226), thanks [@wfraser](https://togithub.com/wfraser)) #### Internal improvements - Revert "add test_issue\_866" ([#1238](https://togithub.com/chronotope/chrono/issues/1238)) - CI: run tests on `i686` and `wasm32-wasi` ([#1237](https://togithub.com/chronotope/chrono/issues/1237)) - CI: Include doctests for code coverage ([#1248](https://togithub.com/chronotope/chrono/issues/1248)) - Move benchmarks to a separate crate ([#1243](https://togithub.com/chronotope/chrono/issues/1243)) This allows us to upgrade the criterion dependency to 5.1 without changing our MSRV. - Add Discord link to README ([#1240](https://togithub.com/chronotope/chrono/issues/1240), backported in [#1256](https://togithub.com/chronotope/chrono/issues/1256)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.28`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.28): 0.4.28 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.27...v0.4.28) This release fixes a test failure on 32-bit targets introduced with 0.4.27, see [https://github.com/chronotope/chrono/issues/1234](https://togithub.com/chronotope/chrono/issues/1234). ### [`v0.4.27`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.27): 0.4.27 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.26...v0.4.27) This release bumps the MSRV from 1.56 to 1.57. This allows us to take advantage of the panicking in const feature. In this release most methods on `NaiveDate` and `NaiveTime` are made const, `NaiveDateTime` and others will follow in a later release. The parser for the `%+` formatting specifier and the `RFC3339` formatting item is switched from a strict to a relaxed parser (see [https://github.com/chronotope/chrono/pull/1145](https://togithub.com/chronotope/chrono/pull/1145)). This matches the existing documentation, and the parser used by `DateTime::from_str`. If you need to validate the input, consider using `DateTime::from_rfc3339`. #### Deprecations - Deprecate `DateTime::{from_local, from_utc}` ([https://github.com/chronotope/chrono/pull/1175](https://togithub.com/chronotope/chrono/pull/1175)) #### Additions - Let `DateTime::signed_duration_since` take argument with `Borrow` ([https://github.com/chronotope/chrono/pull/1119](https://togithub.com/chronotope/chrono/pull/1119)) - Implement `PartialOrd` for `Month` ([https://github.com/chronotope/chrono/pull/999](https://togithub.com/chronotope/chrono/pull/999), thanks [@Munksgaard](https://togithub.com/Munksgaard)) - Add `Ord` and `Eq` for types which already derive `PartialOrd` and `PartialEq` ([https://github.com/chronotope/chrono/pull/1128](https://togithub.com/chronotope/chrono/pull/1128), thanks [@totikom](https://togithub.com/totikom)) - implement `FusedIterator` for `NaiveDateDaysIterator` and `NaiveDateWeeksIterator` ([https://github.com/chronotope/chrono/pull/1134](https://togithub.com/chronotope/chrono/pull/1134)) - Make `NaiveDateDaysIterator` and `NaiveDateWeeksIterator` public ([https://github.com/chronotope/chrono/pull/1134](https://togithub.com/chronotope/chrono/pull/1134)) - Add `FromStr` for `FixedOffset` ([https://github.com/chronotope/chrono/pull/1157](https://togithub.com/chronotope/chrono/pull/1157), thanks [@mcronce](https://togithub.com/mcronce)) - Remove `Tz::Offset: Display` requirement from `DateTime::to_rfc*` ([https://github.com/chronotope/chrono/pull/1160](https://togithub.com/chronotope/chrono/pull/1160)) - More flexible offset formatting (not exposed yet) ([https://github.com/chronotope/chrono/pull/1160](https://togithub.com/chronotope/chrono/pull/1160)) - Make `StrftimeItems` with `unstable-locales` work without allocating ([https://github.com/chronotope/chrono/pull/1152](https://togithub.com/chronotope/chrono/pull/1152)) - Make `NaiveDate::from_ymd_opt` const ([https://github.com/chronotope/chrono/pull/1172](https://togithub.com/chronotope/chrono/pull/1172), thanks [@kamadorueda](https://togithub.com/kamadorueda)) - Implement `Error` trait for `ParseWeekdayError` and `ParseMonthError` ([https://github.com/chronotope/chrono/pull/539](https://togithub.com/chronotope/chrono/pull/539), thanks [@mike-kfed](https://togithub.com/mike-kfed)) - Make methods on `NaiveTime` const, update MSRV to 1.57 ([https://github.com/chronotope/chrono/pull/1080](https://togithub.com/chronotope/chrono/pull/1080)) - Make methods on `NaiveDate` const ([https://github.com/chronotope/chrono/pull/1205](https://togithub.com/chronotope/chrono/pull/1205)) - Implement operations for `core::time::Duration` on `DateTime` types ([https://github.com/chronotope/chrono/pull/1229](https://togithub.com/chronotope/chrono/pull/1229)) #### Fixes - Ensure `timestamp_nanos` panics on overflow in release builds ([https://github.com/chronotope/chrono/pull/1123](https://togithub.com/chronotope/chrono/pull/1123)) - Fix `offset_from_local_datetime` for `wasm_bindgen` ([https://github.com/chronotope/chrono/pull/1131](https://togithub.com/chronotope/chrono/pull/1131)) - Parsing: Consider `%s` to be a timestamp in UTC ([https://github.com/chronotope/chrono/pull/1136](https://togithub.com/chronotope/chrono/pull/1136)) - Don't panic when formatting with `%#z` ([https://github.com/chronotope/chrono/pull/1140](https://togithub.com/chronotope/chrono/pull/1140), thanks [@domodwyer](https://togithub.com/domodwyer)) - Parsing: allow MINUS SIGN (U+2212) in offset ([https://github.com/chronotope/chrono/pull/1087](https://togithub.com/chronotope/chrono/pull/1087), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - Fix locale formatting for `%c` and `%r` ([https://github.com/chronotope/chrono/pull/1165](https://togithub.com/chronotope/chrono/pull/1165)) - Localize decimal point with `unstable-locales` feature ([https://github.com/chronotope/chrono/pull/1168](https://togithub.com/chronotope/chrono/pull/1168)) - Fix panic on macOS 10.12 caused by using version 1 of the TZif file format ([https://github.com/chronotope/chrono/pull/1201](https://togithub.com/chronotope/chrono/pull/1201), thanks to help from [@jfro](https://togithub.com/jfro)) - Fix deserialization of negative timestamps ([https://github.com/chronotope/chrono/pull/1194](https://togithub.com/chronotope/chrono/pull/1194)) - Do not use `Offset`'s `Debug` impl when serializing `DateTime` ([https://github.com/chronotope/chrono/pull/1035](https://togithub.com/chronotope/chrono/pull/1035)) - Allow missing seconds in `NaiveTime::from_str` ([https://github.com/chronotope/chrono/pull/1181](https://togithub.com/chronotope/chrono/pull/1181)) - Do not depend on `android-tzdata` if the `clock` feature is not enabled ([https://github.com/chronotope/chrono/pull/1220](https://togithub.com/chronotope/chrono/pull/1220), thanks [@AlexTMjugador](https://togithub.com/AlexTMjugador)) - Small fixes to the RFC 3339 parsers ([https://github.com/chronotope/chrono/pull/1145](https://togithub.com/chronotope/chrono/pull/1145)) #### Documentation - Add "Errors" and "Panics" sections to API docs ([https://github.com/chronotope/chrono/pull/1120](https://togithub.com/chronotope/chrono/pull/1120)) - Specify licenses in SPDX format ([https://github.com/chronotope/chrono/pull/1132](https://togithub.com/chronotope/chrono/pull/1132), backport of [https://github.com/chronotope/chrono/issues/910](https://togithub.com/chronotope/chrono/issues/910), thanks [@LingMan](https://togithub.com/LingMan)) - Fix `NaiveTime` doc typo ([https://github.com/chronotope/chrono/pull/1146](https://togithub.com/chronotope/chrono/pull/1146), thanks [@zachs18](https://togithub.com/zachs18)) - Clarify nanosecond formatting specifier doc ([https://github.com/chronotope/chrono/pull/1173](https://togithub.com/chronotope/chrono/pull/1173)) - Add warning against combining multiple `Datelike::with_*` ([https://github.com/chronotope/chrono/pull/1199](https://togithub.com/chronotope/chrono/pull/1199)) - Fix typo "accepted" ([https://github.com/chronotope/chrono/pull/1209](https://togithub.com/chronotope/chrono/pull/1209), thanks [@simon04](https://togithub.com/simon04)) - Add some examples to `Utc::now` and `Local::now` ([https://github.com/chronotope/chrono/pull/1192](https://togithub.com/chronotope/chrono/pull/1192)) - Add example to `Weekday::num_days_from_monday` ([https://github.com/chronotope/chrono/pull/1193](https://togithub.com/chronotope/chrono/pull/1193)) - Fix some comments and panic messages ([https://github.com/chronotope/chrono/pull/1221](https://togithub.com/chronotope/chrono/pull/1221), thanks [@umanwizard](https://togithub.com/umanwizard)) #### Internal improvements - `DateTime::to_rfc_*` optimizations ([https://github.com/chronotope/chrono/pull/1200](https://togithub.com/chronotope/chrono/pull/1200)) - Move all tests into modules, fix clippy warnings ([https://github.com/chronotope/chrono/pull/1138](https://togithub.com/chronotope/chrono/pull/1138)) - Offset parsing cleanup ([https://github.com/chronotope/chrono/pull/1158](https://togithub.com/chronotope/chrono/pull/1158)) - Factor out formatting to `format/formatting.rs` ([https://github.com/chronotope/chrono/pull/1156](https://togithub.com/chronotope/chrono/pull/1156)) - Format refactorings ([https://github.com/chronotope/chrono/pull/1198](https://togithub.com/chronotope/chrono/pull/1198)) - Format toml files with taplo ([https://github.com/chronotope/chrono/pull/1117](https://togithub.com/chronotope/chrono/pull/1117), thanks [@tottoto](https://togithub.com/tottoto)) - Stop vendoring `saturating_abs` ([https://github.com/chronotope/chrono/pull/1124](https://togithub.com/chronotope/chrono/pull/1124)) - CI: shell set -eux, use bash ([https://github.com/chronotope/chrono/pull/1103](https://togithub.com/chronotope/chrono/pull/1103), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - Fix dead code error when running dateutils test on Windows ([https://github.com/chronotope/chrono/pull/1125](https://togithub.com/chronotope/chrono/pull/1125)) - Remove `Makefile` ([https://github.com/chronotope/chrono/pull/1133](https://togithub.com/chronotope/chrono/pull/1133)) - CI: Test `wasm-bindgen` feature ([https://github.com/chronotope/chrono/pull/1131](https://togithub.com/chronotope/chrono/pull/1131)) - Stop using deprecated methods in parse module ([https://github.com/chronotope/chrono/pull/1142](https://togithub.com/chronotope/chrono/pull/1142)) - Add formatting benchmarks ([https://github.com/chronotope/chrono/pull/1155](https://togithub.com/chronotope/chrono/pull/1155)) - Feature gate tests instead of methods ([https://github.com/chronotope/chrono/pull/1159](https://togithub.com/chronotope/chrono/pull/1159), [https://github.com/chronotope/chrono/pull/1162](https://togithub.com/chronotope/chrono/pull/1162)) - Parallelize `try_verify_against_date_command` ([https://github.com/chronotope/chrono/pull/1161](https://togithub.com/chronotope/chrono/pull/1161)) - CI: also run integration tests with `no_std` ([https://github.com/chronotope/chrono/pull/1166](https://togithub.com/chronotope/chrono/pull/1166)) - Split ` test_parse ` ([https://github.com/chronotope/chrono/pull/1170](https://togithub.com/chronotope/chrono/pull/1170)) - Remove `#![deny(dead_code)]` ([https://github.com/chronotope/chrono/pull/1187](https://togithub.com/chronotope/chrono/pull/1187)) - Clippy fixes for Rust 1.71 ([https://github.com/chronotope/chrono/pull/1186](https://togithub.com/chronotope/chrono/pull/1186)) - Various small improvements ([https://github.com/chronotope/chrono/pull/1191](https://togithub.com/chronotope/chrono/pull/1191)) - Add unit test for uncovered regions ([https://github.com/chronotope/chrono/pull/1149](https://togithub.com/chronotope/chrono/pull/1149), thanks [@CXWorks](https://togithub.com/CXWorks)) - Don't test the same thing twice in `test_date_extreme_offset` ([https://github.com/chronotope/chrono/pull/1195](https://togithub.com/chronotope/chrono/pull/1195)) - CI: Add workflow code coverage report and upload ([https://github.com/chronotope/chrono/pull/1178](https://togithub.com/chronotope/chrono/pull/1178), [https://github.com/chronotope/chrono/pull/1215](https://togithub.com/chronotope/chrono/pull/1215), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - CI: fail on warnings in `features-check` ([https://github.com/chronotope/chrono/pull/1216](https://togithub.com/chronotope/chrono/pull/1216)) - Switch to windows-bindgen ([https://github.com/chronotope/chrono/pull/1202](https://togithub.com/chronotope/chrono/pull/1202), thanks to help from [@MarijnS95](https://togithub.com/MarijnS95)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.26`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.26): 0.4.26 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.25...v0.4.26) The changes from [#807](https://togithub.com/chronotope/chrono/issues/807) we merged for 0.4.25 unfortunately restricted parsing in a way that was incompatible with earlier 0.4.x releases. We reverted this in [#1113](https://togithub.com/chronotope/chrono/issues/1113). A small amount of other changes were merged since. - Update README ([#1111](https://togithub.com/chronotope/chrono/issues/1111), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Revert backport of [#807](https://togithub.com/chronotope/chrono/issues/807) ([#1113](https://togithub.com/chronotope/chrono/issues/1113), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Update to 2021 edition ([#1109](https://togithub.com/chronotope/chrono/issues/1109), thanks to [@tottoto](https://togithub.com/tottoto)) - Fix `DurationRound` panics from issue [#1010](https://togithub.com/chronotope/chrono/issues/1010) ([#1093](https://togithub.com/chronotope/chrono/issues/1093), thanks to [@pitdicker](https://togithub.com/pitdicker)) - tests: date path consolidate (branch 0.4.x) ([#1090](https://togithub.com/chronotope/chrono/issues/1090), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - Parse tests nanosecond bare dot (branch 0.4.x) ([#1098](https://togithub.com/chronotope/chrono/issues/1098), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - yamllint cleanup lint.yml test.yml ([#1102](https://togithub.com/chronotope/chrono/issues/1102), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - Remove num-iter dependency ([#1107](https://togithub.com/chronotope/chrono/issues/1107), thanks to [@tottoto](https://togithub.com/tottoto)) Thanks on behalf of the chrono team ([@djc](https://togithub.com/djc) and [@esheppa](https://togithub.com/esheppa)) to all contributors! ### [`v0.4.25`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.25): 0.4.25 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.24...v0.4.25) Time for another maintenance release. This release bumps the MSRV to 1.56; given MSRV bumps in chrono's dependencies (notably for syn 2), we felt that it no longer made sense to support any older versions. Feedback welcome in our issue tracker! #### Additions - Bump the MSRV to 1.56 ([#1053](https://togithub.com/chronotope/chrono/issues/1053)) - Apply comments from MSRV bump ([#1026](https://togithub.com/chronotope/chrono/issues/1026), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Remove num-integer dependency ([#1037](https://togithub.com/chronotope/chrono/issues/1037), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `NaiveDateTime::and_utc()` method ([#952](https://togithub.com/chronotope/chrono/issues/952), thanks to [@klnusbaum](https://togithub.com/klnusbaum)) - derive `Hash` for most pub types that also derive `PartialEq` ([#938](https://togithub.com/chronotope/chrono/issues/938), thanks to [@bruceg](https://togithub.com/bruceg)) - Add `parse_and_remainder()` methods ([#1011](https://togithub.com/chronotope/chrono/issues/1011), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `DateTime::fix_offset()` ([#1030](https://togithub.com/chronotope/chrono/issues/1030), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `#[track_caller]` to `LocalResult::unwrap` ([#1046](https://togithub.com/chronotope/chrono/issues/1046), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `#[must_use]` to some methods ([#1007](https://togithub.com/chronotope/chrono/issues/1007), thanks to [@aceArt-GmbH](https://togithub.com/aceArt-GmbH)) - Implement `PartialOrd` for `Month` ([#999](https://togithub.com/chronotope/chrono/issues/999), thanks to [@Munksgaard](https://togithub.com/Munksgaard)) - Add `impl From<NaiveDateTime> for NaiveDate` ([#1012](https://togithub.com/chronotope/chrono/issues/1012), thanks to [@pezcore](https://togithub.com/pezcore)) - Extract timezone info from tzdata file on Android ([#978](https://togithub.com/chronotope/chrono/issues/978), thanks to [@RumovZ](https://togithub.com/RumovZ)) #### Fixes - Prevent string slicing inside char boundaries ([#1024](https://togithub.com/chronotope/chrono/issues/1024), thanks to [@pitdicker](https://togithub.com/pitdicker)) - fix IsoWeek so that its flags are always correct ([#991](https://togithub.com/chronotope/chrono/issues/991), thanks to [@moshevds](https://togithub.com/moshevds)) - Fix out-of-range panic in `NaiveWeek::last_day` ([#1070](https://togithub.com/chronotope/chrono/issues/1070), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Use correct offset in conversion from `Local` to `FixedOffset` ([#1041](https://togithub.com/chronotope/chrono/issues/1041), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix military timezones in RFC 2822 parsing ([#1013](https://togithub.com/chronotope/chrono/issues/1013), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Guard against overflow in NaiveDate::with_\*0 methods ([#1023](https://togithub.com/chronotope/chrono/issues/1023), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix panic in from_num_days_from_ce_opt ([#1052](https://togithub.com/chronotope/chrono/issues/1052), thanks to [@pitdicker](https://togithub.com/pitdicker)) #### Refactoring - Rely on std for getting local time offset ([#1072](https://togithub.com/chronotope/chrono/issues/1072), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Make functions in internals const ([#1043](https://togithub.com/chronotope/chrono/issues/1043), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Refactor windows module in `Local` ([#992](https://togithub.com/chronotope/chrono/issues/992), thanks to [@nekevss](https://togithub.com/nekevss)) - Simplify from_timestamp_millis, from_timestamp_micros ([#1032](https://togithub.com/chronotope/chrono/issues/1032), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Backport [#983](https://togithub.com/chronotope/chrono/issues/983) and [#1000](https://togithub.com/chronotope/chrono/issues/1000) ([#1063](https://togithub.com/chronotope/chrono/issues/1063), thanks to [@pitdicker](https://togithub.com/pitdicker)) #### Documentation - Backport documentation improvements ([#1066](https://togithub.com/chronotope/chrono/issues/1066), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add documentation for %Z quirk ([#1051](https://togithub.com/chronotope/chrono/issues/1051), thanks to [@campbellcole](https://togithub.com/campbellcole)) - Add an example to Weekday ([#1019](https://togithub.com/chronotope/chrono/issues/1019), thanks to [@pitdicker](https://togithub.com/pitdicker)) #### Internal improvements - Gate test on `clock` feature ([#1061](https://togithub.com/chronotope/chrono/issues/1061), thanks to [@pitdicker](https://togithub.com/pitdicker)) - CI: Also run tests with `--no-default-features` ([#1059](https://togithub.com/chronotope/chrono/issues/1059), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Prevent `bench_year_flags_from_year` from being optimized out ([#1034](https://togithub.com/chronotope/chrono/issues/1034), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix test_leap_second during DST transition ([#1064](https://togithub.com/chronotope/chrono/issues/1064), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix warnings when running tests on Windows ([#1038](https://togithub.com/chronotope/chrono/issues/1038), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix tests on AIX ([#1028](https://togithub.com/chronotope/chrono/issues/1028), thanks to [@ecnelises](https://togithub.com/ecnelises)) - Fix doctest warnings, remove mention of deprecated methods from main doc ([#1081](https://togithub.com/chronotope/chrono/issues/1081), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Reformat `test_datetime_parse_from_str` ([#1078](https://togithub.com/chronotope/chrono/issues/1078), thanks to [@pitdicker](https://togithub.com/pitdicker)) - GitHub yml shell `set -eux`, use bash ([#1103](https://togithub.com/chronotope/chrono/issues/1103), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - test: explicitly set `LANG` to `c` in gnu `date` ([#1089](https://togithub.com/chronotope/chrono/issues/1089), thanks to [@scarf005](https://togithub.com/scarf005)) - Switch test to `TryFrom` ([#1086](https://togithub.com/chronotope/chrono/issues/1086), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add test for issue 551 ([#1020](https://togithub.com/chronotope/chrono/issues/1020), thanks to [@pitdicker](https://togithub.com/pitdicker)) - RFC 2822 single-letter obsolete tests ([#1014](https://togithub.com/chronotope/chrono/issues/1014), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - \[CI] Lint Windows target and documentation links ([#1062](https://togithub.com/chronotope/chrono/issues/1062), thanks to [@pitdicker](https://togithub.com/pitdicker)) - add test_issue\_866 ([#1077](https://togithub.com/chronotope/chrono/issues/1077), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - Remove AUTHORS metadata ([#1074](https://togithub.com/chronotope/chrono/issues/1074)) On behalf of [@djc](https://togithub.com/djc) and [@esheppa](https://togithub.com/esheppa), thanks to all contributors! ### [`v0.4.24`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.24): 0.4.24 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.23...v0.4.24) This is a small maintenance release with accumulated fixes and improvements. - Fix doc on `Days::new()` to refer to days, not months ([#874](https://togithub.com/chronotope/chrono/issues/874), thanks to [@brotskydotcom](https://togithub.com/brotskydotcom)) - Clarify out of range value for `from_timestamp_opt()` ([#879](https://togithub.com/chronotope/chrono/issues/879), thanks to [@xmo-odoo](https://togithub.com/xmo-odoo)) - Add `format_localized()` for `NaiveDate` ([#881](https://togithub.com/chronotope/chrono/issues/881), thanks to [@mseele](https://togithub.com/mseele)) - Fix bug in `Add`/`Sub` `Days`, add tests with DST timezone ([#878](https://togithub.com/chronotope/chrono/issues/878)) - Make `NaiveTime::MIN` public ([#890](https://togithub.com/chronotope/chrono/issues/890)) - Fix `from_timestamp_millis()` implementation and add more tests ([#885](https://togithub.com/chronotope/chrono/issues/885)) - Fix typo in docstrings ([#897](https://togithub.com/chronotope/chrono/issues/897), thanks to [@dandxy89](https://togithub.com/dandxy89)) - Add test proving that [#903](https://togithub.com/chronotope/chrono/issues/903) is fixed in 0.4.x head ([#905](https://togithub.com/chronotope/chrono/issues/905), thanks to [@umanwizard](https://togithub.com/umanwizard)) - Add `from_timestamp_micros()` function ([#906](https://togithub.com/chronotope/chrono/issues/906), thanks to [@umanwizard](https://togithub.com/umanwizard)) - Check cargo-deny in CI ([#909](https://togithub.com/chronotope/chrono/issues/909)) - Derive `Hash` for most pub types that also derive `PartialEq` ([#938](https://togithub.com/chronotope/chrono/issues/938), thanks to [@bruceg](https://togithub.com/bruceg)) - Update deprecated methods in `from_utc()` example ([#939](https://togithub.com/chronotope/chrono/issues/939), thanks to [@greg-el](https://togithub.com/greg-el)) - Fix panic in `DateTime::checked_add_days()` ([#942](https://togithub.com/chronotope/chrono/issues/942), thanks to [@Ekleog](https://togithub.com/Ekleog)) - More documentation for dates before 1 BCE or after 9999 CE ([#950](https://togithub.com/chronotope/chrono/issues/950), thanks to [@cgit](https://togithub.com/cgit)) - Improve `FixedOffset` docs ([#953](https://togithub.com/chronotope/chrono/issues/953), thanks to [@klnusbaum](https://togithub.com/klnusbaum)) - Add chrono-fuzz to CI and update its libfuzzer-sys dependency ([#968](https://togithub.com/chronotope/chrono/issues/968), thanks to [@LingMan](https://togithub.com/LingMan)) - Fixes to parsing and calculation of week numbers ([#966](https://togithub.com/chronotope/chrono/issues/966), thanks to [@raphaelroosz](https://togithub.com/raphaelroosz)) - Make iana-time-zone a target specific dependency ([#980](https://togithub.com/chronotope/chrono/issues/980), thanks to [@krtab](https://togithub.com/krtab)) - Make eligible functions `const` ([#984](https://togithub.com/chronotope/chrono/issues/984), thanks to [@tormeh](https://togithub.com/tormeh)) Thanks to all contributors from the chrono team, [@esheppa](https://togithub.com/esheppa) and [@djc](https://togithub.com/djc). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/sammyfilly/Nextjs).

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [chrono](https://togithub.com/chronotope/chrono) | dependencies | patch | `0.4` -> `0.4.38` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>chronotope/chrono (chrono)</summary> ### [`v0.4.38`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.38) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.37...v0.4.38) This release bring a ca. 20% improvement to the performance of the formatting code, and a convenient `days_since` method for the `Weekday` type. Chrono 0.4.38 also removes the long deprecated `rustc-serialize` feature. Support for `rustc-serialize` will be [soft-destabilized in the next Rust edition](https://togithub.com/rust-lang/rust/pull/116016). Removing the feature will not break existing users of the feature; Cargo will just not update dependents that rely on it to newer versions of chrono. In chrono 0.4.36 we made an accidental breaking change by switching to `derive(Copy)` for `DateTime` instead of a manual implementation. It is reverted in this release. ### Removals - Remove `rustc-serialize` feature ([#1548](https://togithub.com/chronotope/chrono/issues/1548), thanks [@workingjubilee](https://togithub.com/workingjubilee)) ### Additions - Add `Weekday::days_since` ([#1249](https://togithub.com/chronotope/chrono/issues/1249), based on [#216](https://togithub.com/chronotope/chrono/issues/216) by [@clarfonthey](https://togithub.com/clarfonthey)) - Add `TimeDelta::checked_mul` and `TimeDelta::checked_div` ([#1565](https://togithub.com/chronotope/chrono/issues/1565), thanks [@Zomtir](https://togithub.com/Zomtir)) ### Fixes - Return error when rounding with a zero duration ([#1474](https://togithub.com/chronotope/chrono/issues/1474), thanks [@Dav1dde](https://togithub.com/Dav1dde)) - Manually implement `Copy` for `DateTime` if offset is `Copy` ([#1573](https://togithub.com/chronotope/chrono/issues/1573)) ### Internal - Inline `test_encodable_json` and `test_decodable_json` functions ([#1550](https://togithub.com/chronotope/chrono/issues/1550)) - CI: Reduce combinations in `cargo hack check` ([#1553](https://togithub.com/chronotope/chrono/issues/1553)) - Refactor formatting code ([#1335](https://togithub.com/chronotope/chrono/issues/1335)) - Optimize number formatting ([#1558](https://togithub.com/chronotope/chrono/issues/1558)) - Only package files needed for building and testing ([#1554](https://togithub.com/chronotope/chrono/issues/1554)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.37`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.37) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.36...v0.4.37) Version 0.4.36 introduced an unexpected breaking change and was yanked. In it `LocalResult` was renamed to `MappedLocalTime` to avoid the impression that it is a `Result` type were some of the results are errors. For backwards compatibility a type alias with the old name was added. As it turns out there is one case where a type alias behaves differently from the regular enum: you can't import enum variants from a type alias with `use chrono::LocalResult::*`. With 0.4.37 we make the new name `MappedLocalTime` the alias, but keep using it in function signatures and the documentation as much as possible. See also the release notes of [chrono 0.4.36](https://togithub.com/chronotope/chrono/releases/tag/v0.4.36) from yesterday for the yanked release. ### [`v0.4.36`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.36) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.35...v0.4.36) This release un-deprecates the methods on `TimeDelta` that were deprecated with the 0.4.35 release because of the churn they are causing for the ecosystem. New is the `DateTime::with_time()` method. As an example of when it is useful: ```rust use chrono::{Local, NaiveTime}; // Today at 12:00:00 let today_noon = Local::now().with_time(NaiveTime::from_hms_opt(12, 0, 0).unwrap()); ``` ### Additions - Add `DateTime::with_time()` ([#1510](https://togithub.com/chronotope/chrono/issues/1510)) ### Deprecations - Revert `TimeDelta` deprecations ([#1543](https://togithub.com/chronotope/chrono/issues/1543)) - Deprecate `TimeStamp::timestamp_subsec_nanos`, which was missed in the 0.4.35 release ([#1486](https://togithub.com/chronotope/chrono/issues/1486)) ### Documentation - Correct version number of deprecation notices ([#1486](https://togithub.com/chronotope/chrono/issues/1486)) - Fix some typos ([#1505](https://togithub.com/chronotope/chrono/issues/1505)) - Slightly improve serde documentation ([#1519](https://togithub.com/chronotope/chrono/issues/1519)) - Main documentation: simplify links and reflow text ([#1535](https://togithub.com/chronotope/chrono/issues/1535)) ### Internal - CI: Lint benchmarks ([#1489](https://togithub.com/chronotope/chrono/issues/1489)) - Remove unnessary `Copy` and `Send` impls ([#1492](https://togithub.com/chronotope/chrono/issues/1492), thanks [@erickt](https://togithub.com/erickt)) - Backport streamlined `NaiveDate` unit tests ([#1500](https://togithub.com/chronotope/chrono/issues/1500), thanks [@Zomtir](https://togithub.com/Zomtir)) - Rename `LocalResult` to `TzResolution`, add alias ([#1501](https://togithub.com/chronotope/chrono/issues/1501)) - Update windows-bindgen to 0.55 ([#1504](https://togithub.com/chronotope/chrono/issues/1504)) - Avoid duplicate imports, which generate warnings on nightly ([#1507](https://togithub.com/chronotope/chrono/issues/1507)) - Add extra debug assertions to `NaiveDate::from_yof` ([#1518](https://togithub.com/chronotope/chrono/issues/1518)) - Some small simplifications to `DateTime::date_naive` and `NaiveDate::diff_months` ([#1530](https://togithub.com/chronotope/chrono/issues/1530)) - Remove `unwrap` in Unix `Local` type ([#1533](https://togithub.com/chronotope/chrono/issues/1533)) - Use different method to ignore feature-dependent doctests ([#1534](https://togithub.com/chronotope/chrono/issues/1534)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.35`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.35) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.34...v0.4.35) Most of our efforts have shifted to improving the API for a 0.5 release, for which cleanups and refactorings are landing on the 0.4.x branch. The most significant changes in this release are two sets of deprecations. - We deprecated all timestamp-related methods on `NaiveDateTime`. The reason is that a timestamp is defined to be in UTC. The `NaiveDateTime` type doesn't know the offset from UTC, so it was technically wrong to have these methods. The alternative is to use the similar methods on the `DateTime<Utc>` type, or from the `TimeZone` trait. Converting from `NaiveDateTime` to `DateTime<Utc>` is simple with `.and_utc()`, and in the other direction with `.naive_utc()`. - The panicking constructors of `TimeDelta` (the new name of the `Duration` type) are deprecated. This was the last part of chrono that defaulted to panicking on error, dating from before rust 1.0. - A nice change is that `NaiveDate` now includes a niche. So now `Option<NaiveDate>`, `Option<NaiveDateTime>` and `Option<DateTime<Tz>>` are the same size as their base types. - `format::Numeric` and `format::Fixed` are marked as `non_exhaustive`. This will allow us to improve our formatting and parsing support, and we have reason to believe this breaking change will have little to no impact on users. ### Additions - Add `DateTime::{from_timestamp_micros, from_timestamp_nanos}` ([#1234](https://togithub.com/chronotope/chrono/issues/1234)) - Add getters to `Parsed` ([#1465](https://togithub.com/chronotope/chrono/issues/1465)) ### Deprecations - Deprecate timestamp methods on `NaiveDateTime` ([#1473](https://togithub.com/chronotope/chrono/issues/1473)) - Deprecate panicking constructors of `TimeDelta` ([#1450](https://togithub.com/chronotope/chrono/issues/1450)) ### Changes/fixes - Use `NonZeroI32` inside `NaiveDate` ([#1207](https://togithub.com/chronotope/chrono/issues/1207)) - Mark `format::Numeric` and `format::Fixed` as `non_exhaustive` ([#1430](https://togithub.com/chronotope/chrono/issues/1430)) - `Parsed` fixes to error values ([#1439](https://togithub.com/chronotope/chrono/issues/1439)) - Use `overflowing_naive_local` in `DateTime::checked_add*` ([#1333](https://togithub.com/chronotope/chrono/issues/1333)) - Do complete range checks in `Parsed::set_*` ([#1465](https://togithub.com/chronotope/chrono/issues/1465)) ### Documentation - Rustfmt doctests ([#1452](https://togithub.com/chronotope/chrono/issues/1452)) - Improve docs for crate features ([#1455](https://togithub.com/chronotope/chrono/issues/1455), thanks [@edmorley](https://togithub.com/edmorley)) - Add more documentation and examples to `Parsed` ([#1439](https://togithub.com/chronotope/chrono/issues/1439)) ### Internal - Refactor `internals` module ([#1428](https://togithub.com/chronotope/chrono/issues/1428), [#1429](https://togithub.com/chronotope/chrono/issues/1429), [#1431](https://togithub.com/chronotope/chrono/issues/1431), [#1432](https://togithub.com/chronotope/chrono/issues/1432), [#1433](https://togithub.com/chronotope/chrono/issues/1433), [#1438](https://togithub.com/chronotope/chrono/issues/1438)) - CI: test cross-compiling to `x86_64-unknown-illumos` instead of Solaris ([#1437](https://togithub.com/chronotope/chrono/issues/1437)) - CI: lint Windows target, fix clippy warning ([#1441](https://togithub.com/chronotope/chrono/issues/1441)) - CI: only run `cargo hack check` on Linux ([#1442](https://togithub.com/chronotope/chrono/issues/1442)) - Update windows-bindgen to 0.54 ([#1462](https://togithub.com/chronotope/chrono/issues/1462), [#1483](https://togithub.com/chronotope/chrono/issues/1483)) - Simplify error value of `parse_internal` ([#1459](https://togithub.com/chronotope/chrono/issues/1459)) - Simplify `SerdeError` ([#1458](https://togithub.com/chronotope/chrono/issues/1458)) - Simplify `NaiveDate::from_isoywd` a bit ([#1464](https://togithub.com/chronotope/chrono/issues/1464)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.34`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.34) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.33...v0.4.34) ### Notable changes - In chrono 0.4.34 we finished the work to make all methods const where doing so is supported by rust 1.61. - We renamed the `Duration` type to `TimeDelta`. This removes the confusion between chrono's type and the later `Duration` type in the standard library. It will remain available under the old name as a type alias for compatibility. - The Windows implementation of `Local` is rewritten. The new version avoids panics when the date is outside of the range supported by windows (the years 1601 to 30828), and gives more accurate results during DST transitions. - The `Display` format of `TimeDelta` is modified to conform better to ISO 8601. Previously it converted all values greater than 24 hours to a value with days. This is not correct, as doing so changes the duration from an 'accurate' to a 'nominal' representation to use ISO 8601 terms. ### Fixes - Add missing range check in `TimeDelta::milliseconds` ([#1385](https://togithub.com/chronotope/chrono/issues/1385), thanks [@danwilliams](https://togithub.com/danwilliams)) - Remove check for `DurationExceedsTimestamp` in `DurationRound` ([#1403](https://togithub.com/chronotope/chrono/issues/1403), thanks [@joroKr21](https://togithub.com/joroKr21)) - Fix localized formatting with `%X` ([https://github.com/chronotope/pure-rust-locales/pull/12](https://togithub.com/chronotope/pure-rust-locales/pull/12), [#1420](https://togithub.com/chronotope/chrono/issues/1420)) - Windows: base implementation on `GetTimeZoneInformationForYear` ([#1017](https://togithub.com/chronotope/chrono/issues/1017)) ### Additions - Add `TimeDelta::try_milliseconds` ([#1385](https://togithub.com/chronotope/chrono/issues/1385), thanks [@danwilliams](https://togithub.com/danwilliams)) - Add `TimeDelta::new` ([#1337](https://togithub.com/chronotope/chrono/issues/1337)) - Add `StrftimeItems::{parse, parse_to_owned}` and more documentation ([#1184](https://togithub.com/chronotope/chrono/issues/1184)) - More standard traits and documentation for `format::Locale` (via [https://github.com/chronotope/pure-rust-locales/pull/8](https://togithub.com/chronotope/pure-rust-locales/pull/8)) ### Changes - Rename `Duration` to `TimeDelta`, add type alias ([#1406](https://togithub.com/chronotope/chrono/issues/1406)) - Make `TimeDelta` methods const ([#1337](https://togithub.com/chronotope/chrono/issues/1337)) - Make remaining methods of `NaiveDate`, `NaiveWeek`, `NaiveTime` and `NaiveDateTime` const where possible ([#1337](https://togithub.com/chronotope/chrono/issues/1337)) - Make methods on `DateTime` const where possible ([#1400](https://togithub.com/chronotope/chrono/issues/1400)) - Make `Display` format of `TimeDelta` conform better to ISO 8601 ([#1328](https://togithub.com/chronotope/chrono/issues/1328)) ### Documentation - Fix the formatting of `timestamp_micros`'s Example doc ([#1338](https://togithub.com/chronotope/chrono/issues/1338) via [#1386](https://togithub.com/chronotope/chrono/issues/1386), thanks [@emikitas](https://togithub.com/emikitas)) - Specify branch for GitHub Actions badge and fix link ([#1388](https://togithub.com/chronotope/chrono/issues/1388)) - Don't mention some deprecated methods in docs ([#1395](https://togithub.com/chronotope/chrono/issues/1395)) - Remove stray documentation from main ([#1397](https://togithub.com/chronotope/chrono/issues/1397)) - Improved documentation of `TimeDelta` constructors ([#1385](https://togithub.com/chronotope/chrono/issues/1385), thanks [@danwilliams](https://togithub.com/danwilliams)) ### Internal - Switch branch names: 0.4.x releases are the `main` branch, work on 0.5 happens in the `0.5.x` branch ([#1390](https://togithub.com/chronotope/chrono/issues/1390), [#1402](https://togithub.com/chronotope/chrono/issues/1402)). - Don't use deprecated method in `impl Arbitrary for DateTime` and set up CI test ([#1336](https://togithub.com/chronotope/chrono/issues/1336)) - Remove workaround for Rust < 1.61 ([#1393](https://togithub.com/chronotope/chrono/issues/1393)) - Bump `codecov/codecov-action` from 3 to 4 ([#1404](https://togithub.com/chronotope/chrono/issues/1404)) - Remove partial support for handling `-0000` offset ([#1411](https://togithub.com/chronotope/chrono/issues/1411)) - Move `TOO_LONG` error out of `parse_internal` ([#1419](https://togithub.com/chronotope/chrono/issues/1419)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.33`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.33) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.32...v0.4.33) This release fixes the broken docrs.rs build of [chrono 0.4.32](https://togithub.com/chronotope/chrono/releases/tag/v0.4.32). #### What's Changed - Make `rkyv` feature imply `size_32` ([#1383](https://togithub.com/chronotope/chrono/issues/1383)) - Fixed typo in `Duration::hours()` exception ([#1384](https://togithub.com/chronotope/chrono/issues/1384), thanks [@danwilliams](https://togithub.com/danwilliams)) ### [`v0.4.32`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.32) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.31...v0.4.32) In this release we shipped part of the effort to reduce the number of methods that could unexpectedly panic, notably for the `DateTime` and `Duration` types. Chrono internally stores the value of a `DateTime` in UTC, and transparently converts it to the local value as required. For example adding a second to a `DateTime` needs to be done in UTC to get the correct result, but adding a day needs to be done in local time to be correct. What happens when the value is near the edge of the representable range, and the implicit conversions pushes it beyond the representable range? *Many* methods could panic on such inputs, including formatting the value for `Debug` output. In chrono 0.4.32 the range of `NaiveDate`, `NaiveDateTime` and `DateTime` is made slightly smaller. This allows us to always do the implicit conversion, and in many cases return the expected result. Specifically the range is now from January 1, -262144 until December 31, 262143, one year less on both sides than before. We expect this may trip up tests if you hardcoded the `MIN` and `MAX` dates. `Duration` had a similar issue. The range of this type was pretty arbitrary picked to match the range of an `i64` in milliseconds. Negating an `i64::MIN` pushes a value out of range, and in the same way negating `Duration::MIN` could push it out of our defined range and cause a panic. This turns out to be somewhat common and hidden behind many layers of abstraction. We adjusted the type to have a minimum value of `-Duration::MAX` instead and prevent the panic case. Other highlights: - `Duration` gained new fallible initialization methods. - Better support for `rkyv`. - Most methods on `NaiveDateTime` are now const. - We had to bump our MSRV to 1.61 to keep building with our dependencies. This will also allow us to make more methods on `DateTime` const in a future release. Complete list of changes: #### Fixes - Fix panic in `TimeZone::from_local_datetime` ([#1071](https://togithub.com/chronotope/chrono/issues/1071)) - Fix out of range panics in `DateTime` getters and setters ([#1317](https://togithub.com/chronotope/chrono/issues/1317), [#1329](https://togithub.com/chronotope/chrono/issues/1329)) #### Additions - Add `NaiveDateTime::checked_(add|sub)_offset` ([#1313](https://togithub.com/chronotope/chrono/issues/1313)) - Add `DateTime::to_utc` ([#1325](https://togithub.com/chronotope/chrono/issues/1325)) - Derive `Default` for `Duration` ([#1327](https://togithub.com/chronotope/chrono/issues/1327)) - Add `Duration::subsec_nanos` ([#1327](https://togithub.com/chronotope/chrono/issues/1327)) - Add `try_*` builders to `Duration` ([#1327](https://togithub.com/chronotope/chrono/issues/1327)) - Implement `AddAssign` and `SubAssign` for `Duration` ([#1327](https://togithub.com/chronotope/chrono/issues/1327)) - Make methods on `NaiveDateTime` const where possible ([#1286](https://togithub.com/chronotope/chrono/issues/1286)) - Split `clock` feature into `clock` and `now` ([#1343](https://togithub.com/chronotope/chrono/issues/1343), thanks [@mmastrac](https://togithub.com/mmastrac)) - Add `From<NaiveDate>` for `NaiveDateTime` ([#1355](https://togithub.com/chronotope/chrono/issues/1355), thanks [@dcechano](https://togithub.com/dcechano)) - Add `NaiveDateTime::from_timestamp_nanos` ([#1357](https://togithub.com/chronotope/chrono/issues/1357), thanks [@Ali-Mirghasemi](https://togithub.com/Ali-Mirghasemi)) - Add `Months::num_months()` and `num_years()` ([#1373](https://togithub.com/chronotope/chrono/issues/1373), thanks [@danwilliams](https://togithub.com/danwilliams)) - Add `DateTime<Utc>::from_timestamp_millis` ([#1374](https://togithub.com/chronotope/chrono/issues/1374), thanks [@xmakro](https://togithub.com/xmakro)) #### Changes - Fix panic in `Duration::MIN.abs()` (adjust `Duration::MIN` by 1 millisecond) ([#1334](https://togithub.com/chronotope/chrono/issues/1334)) - Bump MSRV to 1.61 ([#1347](https://togithub.com/chronotope/chrono/issues/1347)) - Update windows-targets requirement from 0.48 to 0.52 ([#1360](https://togithub.com/chronotope/chrono/issues/1360)) - Update windows-bindgen to 0.52 ([#1379](https://togithub.com/chronotope/chrono/issues/1379)) #### Deprecations - Deprecate standalone `format` functions ([#1306](https://togithub.com/chronotope/chrono/issues/1306)) #### Documentation - Improve doc comment and tests for timestamp_nanos_opt ([#1299](https://togithub.com/chronotope/chrono/issues/1299), thanks [@mlegner](https://togithub.com/mlegner)) - Switch to `doc_auto_cfg` ([#1305](https://togithub.com/chronotope/chrono/issues/1305), [#1326](https://togithub.com/chronotope/chrono/issues/1326)) - Document panics in `Add`/`Sub` impls and use `expect` ([#1316](https://togithub.com/chronotope/chrono/issues/1316)) - Improve types listed in top-level documentation ([#1274](https://togithub.com/chronotope/chrono/issues/1274)) - Improve deprecation note of `TimeZone::datetime_from_str` ([#1342](https://togithub.com/chronotope/chrono/issues/1342), thanks [@tmccombs](https://togithub.com/tmccombs)) - Fix typos in `Datelike` impl for `DateTime` ([#1376](https://togithub.com/chronotope/chrono/issues/1376), thanks [@ElectrifyPro](https://togithub.com/ElectrifyPro)) #### Rkyv support - Export `Archived*` types in `rkyv` module ([#1304](https://togithub.com/chronotope/chrono/issues/1304)) - Duplicate derives on `Archived*` types ([#1271](https://togithub.com/chronotope/chrono/issues/1271), thanks [@Awpteamoose](https://togithub.com/Awpteamoose)) - Archive derive of PartialEq for rkyv ([#959](https://togithub.com/chronotope/chrono/issues/959), thanks [@mkatychev](https://togithub.com/mkatychev)) - Expose rkyv features as features for chrono users ([#1368](https://togithub.com/chronotope/chrono/issues/1368), thanks [@gz](https://togithub.com/gz)) #### Changes to unstable features - Don't let `unstable-locales` imply the `alloc` feature ([#1307](https://togithub.com/chronotope/chrono/issues/1307)) - Remove `format::{format_localized, format_item_localized}` ([#1311](https://togithub.com/chronotope/chrono/issues/1311)) - Inline `write_rfc2822_inner`, don't localize ([#1322](https://togithub.com/chronotope/chrono/issues/1322)) #### Internal - Add benchmark for `DateTime::with_*` ([#1309](https://togithub.com/chronotope/chrono/issues/1309)) - Fix `*_DAYS_FROM_YEAR_0` calculation ([#1312](https://togithub.com/chronotope/chrono/issues/1312)) - Add `NaiveTime::overflowing_(add|sub)_offset` ([#1310](https://togithub.com/chronotope/chrono/issues/1310)) - Rewrite `DateTime::overflowing_(add|sub)_offset` ([#1069](https://togithub.com/chronotope/chrono/issues/1069)) - Tests calling date command `set env LC_ALL` ([#1315](https://togithub.com/chronotope/chrono/issues/1315), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - Update `deny.toml` ([#1320](https://togithub.com/chronotope/chrono/issues/1320)) - Bump actions/setup-node from 3 to 4 ([#1346](https://togithub.com/chronotope/chrono/issues/1346)) - test.yml remove errant `with: node-version` ([#1352](https://togithub.com/chronotope/chrono/issues/1352), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - CI Linting: Fix missing sources checkout in `toml` job ([#1371](https://togithub.com/chronotope/chrono/issues/1371), thanks [@gibbz00](https://togithub.com/gibbz00)) - Silence clippy lint for test code with Rust 1.74.0 ([#1362](https://togithub.com/chronotope/chrono/issues/1362)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.31`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.31) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.30...v0.4.31) Another maintenance release. It was not a planned effort to improve our support for UNIX timestamps, yet most PRs seem related to this. ##### Deprecations - Deprecate `timestamp_nanos` in favor of the non-panicking `timestamp_nanos_opt` ([#1275](https://togithub.com/chronotope/chrono/issues/1275)) ##### Additions - Add `DateTime::<Utc>::from_timestamp` ([#1279](https://togithub.com/chronotope/chrono/issues/1279), thanks [@demurgos](https://togithub.com/demurgos)) - Add `TimeZone::timestamp_micros` ([#1285](https://togithub.com/chronotope/chrono/issues/1285), thanks [@emikitas](https://togithub.com/emikitas)) - Add `DateTime<Tz>::timestamp_nanos_opt` and `NaiveDateTime::timestamp_nanos_opt` ([#1275](https://togithub.com/chronotope/chrono/issues/1275)) - Add `UNIX_EPOCH` constants ([#1291](https://togithub.com/chronotope/chrono/issues/1291)) ##### Fixes - Format day of month in RFC 2822 without padding ([#1272](https://togithub.com/chronotope/chrono/issues/1272)) - Don't allow strange leap seconds which are not on a minute boundary initialization methods ([#1283](https://togithub.com/chronotope/chrono/issues/1283)) This makes many methods a little more strict: - `NaiveTime::from_hms_milli` - `NaiveTime::from_hms_milli_opt` - `NaiveTime::from_hms_micro` - `NaiveTime::from_hms_micro_opt` - `NaiveTime::from_hms_nano` - `NaiveTime::from_hms_nano_opt` - `NaiveTime::from_num_seconds_from_midnight` - `NaiveTime::from_num_seconds_from_midnight_opt` - `NaiveDate::and_hms_milli` - `NaiveDate::and_hms_milli_opt` - `NaiveDate::and_hms_micro` - `NaiveDate::and_hms_micro_opt` - `NaiveDate::and_hms_nano` - `NaiveDate::and_hms_nano_opt` - `NaiveDateTime::from_timestamp` - `NaiveDateTime::from_timestamp_opt` - `TimeZone::timestamp` - `TimeZone::timestamp_opt` - Fix underflow in `NaiveDateTime::timestamp_nanos_opt` ([#1294](https://togithub.com/chronotope/chrono/issues/1294), thanks [@crepererum](https://togithub.com/crepererum)) ##### Documentation - Add more documentation about the RFC 2822 obsolete date format ([#1267](https://togithub.com/chronotope/chrono/issues/1267)) ##### Internal - Remove internal `__doctest` feature and `doc_comment` dependency ([#1276](https://togithub.com/chronotope/chrono/issues/1276)) - CI: Bump `actions/checkout` from 3 to 4 ([#1280](https://togithub.com/chronotope/chrono/issues/1280)) - Optimize `NaiveDate::add_days` for small values ([#1214](https://togithub.com/chronotope/chrono/issues/1214)) - Upgrade `pure-rust-locales` to 0.7.0 ([#1288](https://togithub.com/chronotope/chrono/issues/1288), thanks [@jeremija](https://togithub.com/jeremija) wo did good improvements on `pure-rust-locales`) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.30`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.30) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.29...v0.4.30) In this release, we have decided to swap out the `chrono::Duration` type (which has been a re-export of time 0.1 `Duration` type) with our own definition, which exposes a strict superset of the `time::Duration` API. This helps avoid warnings about the [CVE-2020-26235] and [RUSTSEC-2020-0071] advisories for downstream users and allows us to improve the `Duration` API going forward. While this is technically a SemVer-breaking change, we expect the risk of downstream users experiencing actual incompatibility to be exceedingly limited (see [our analysis](https://togithub.com/chronotope/chrono/pull/1095#issuecomment-1571716955) of public code using a crater-like experiment), and not enough justification for the large ecosystem churn of a 0.5 release. If you have any feedback on these changes, please let us know in [#1268](https://togithub.com/chronotope/chrono/issues/1268). ##### Additions - Add `NaiveDate::leap_year` ([#1261](https://togithub.com/chronotope/chrono/issues/1261)) ##### Documentation - Update main documentation from README ([#1260](https://togithub.com/chronotope/chrono/issues/1260), thanks [@Stygmates](https://togithub.com/Stygmates)) - Add history of relation between chrono and time 0.1 to documentation ([https://github.com/chronotope/chrono/pull/1264](https://togithub.com/chronotope/chrono/pull/1264), [https://github.com/chronotope/chrono/pull/1266](https://togithub.com/chronotope/chrono/pull/1266)) - Clarify `Timelike::num_seconds_from_midnight` is a simple mapping ([#1255](https://togithub.com/chronotope/chrono/issues/1255)) #### Relation between chrono and time 0.1 Rust first had a `time` module added to `std` in its 0.7 release. It later moved to `libextra`, and then to a `libtime` library shipped alongside the standard library. In 2014 work on chrono started in order to provide a full-featured date and time library in Rust. Some improvements from chrono made it into the standard library; notably, `chrono::Duration` was included as `std::time::Duration` ([rust#15934]) in 2014. In preparation of Rust 1.0 at the end of 2014 `libtime` was moved out of the Rust distro and into the `time` crate to eventually be redesigned ([rust#18832], [rust#18858]), like the `num` and `rand` crates. Of course chrono kept its dependency on this `time` crate. `time` started re-exporting `std::time::Duration` during this period. Later, the standard library was changed to have a more limited unsigned `Duration` type ([rust#24920], [RFC 1040]), while the `time` crate kept the full functionality with `time::Duration`. `time::Duration` had been a part of chrono's public API. By 2016 `time` 0.1 lived under the `rust-lang-deprecated` organisation and was not actively maintained ([time#136]). chrono absorbed the platform functionality and `Duration` type of the `time` crate in [chrono#478] (the work started in [chrono#286]). In order to preserve compatibility with downstream crates depending on `time` and `chrono` sharing a `Duration` type, chrono kept depending on time 0.1. chrono offered the option to opt out of the `time` dependency by disabling the `oldtime` feature (swapping it out for an effectively similar chrono type). In 2019, [@jhpratt](https://togithub.com/jhpratt) took over maintenance on the `time` crate and released what amounts to a new crate as `time` 0.2. [rust#15934]: https://togithub.com/rust-lang/rust/pull/15934 [rust#18832]: https://togithub.com/rust-lang/rust/pull/18832#issuecomment-62448221 [rust#18858]: https://togithub.com/rust-lang/rust/pull/18858 [rust#24920]: https://togithub.com/rust-lang/rust/pull/24920 [RFC 1040]: https://rust-lang.github.io/rfcs/1040-duration-reform.html [time#136]: https://togithub.com/time-rs/time/issues/136 [chrono#286]: https://togithub.com/chronotope/chrono/pull/286 [chrono#478]: https://togithub.com/chronotope/chrono/pull/478 ##### Security advisories In November of 2020 [CVE-2020-26235] and [RUSTSEC-2020-0071] were opened against the `time` crate. [@quininer](https://togithub.com/quininer) had found that calls to `localtime_r` may be unsound ([chrono#499]). Eventually, almost a year later, this was also made into a security advisory against chrono as [RUSTSEC-2020-0159], which had platform code similar to `time`. On Unix-like systems a process is given a timezone id or description via the `TZ` environment variable. We need this timezone data to calculate the current local time from a value that is in UTC, such as the time from the system clock. `time` 0.1 and chrono used the POSIX function `localtime_r` to do the conversion to local time, which reads the `TZ` variable. Rust assumes the environment to be writable and uses locks to access it from multiple threads. Some other programming languages and libraries use similar locking strategies, but these are typically not shared across languages. More importantly, POSIX declares modifying the environment in a multi-threaded process as unsafe, and `getenv` in libc can't be changed to take a lock because it returns a pointer to the data (see [rust#27970] for more discussion). Since version 4.20 chrono no longer uses `localtime_r`, instead using Rust code to query the timezone (from the `TZ` variable or via `iana-time-zone` as a fallback) and work with data from the system timezone database directly. The code for this was forked from the [tz-rs crate] by [@x-hgg-x](https://togithub.com/x-hgg-x). As such, chrono now respects the Rust lock when reading the `TZ` environment variable. In general, code should avoid modifying the environment. [CVE-2020-26235]: https://nvd.nist.gov/vuln/detail/CVE-2020-26235 [RUSTSEC-2020-0071]: https://rustsec.org/advisories/RUSTSEC-2020-0071 [chrono#499]: https://togithub.com/chronotope/chrono/pull/499 [RUSTSEC-2020-0159]: https://rustsec.org/advisories/RUSTSEC-2020-0159.html [rust#27970]: https://togithub.com/rust-lang/rust/issues/27970 [chrono#677]: https://togithub.com/chronotope/chrono/pull/677 [tz-rs crate]: https://crates.io/crates/tz-rs ##### Removing time 0.1 Because time 0.1 has been unmaintained for years, however, the security advisory mentioned above has not been addressed. While chrono maintainers were careful not to break backwards compatibility with the `time::Duration` type, there has been a long stream of issues from users inquiring about the time 0.1 dependency with the vulnerability. We investigated the potential breakage of removing the time 0.1 dependency in [chrono#1095] using a crater-like experiment and determined that the potential for breaking (public) dependencies is very low. We reached out to those few crates that did still depend on compatibility with time 0.1. As such, for chrono 0.4.30 we have decided to swap out the time 0.1 `Duration` implementation for a local one that will offer a strict superset of the existing API going forward. This will prevent most downstream users from being affected by the security vulnerability in time 0.1 while minimizing the ecosystem impact of semver-incompatible version churn. [chrono#1095]: https://togithub.com/chronotope/chrono/pull/1095 Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.29`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.29) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.28...v0.4.29) This release fixes a panic introduced in chrono 0.4.27 in `FromStr<DateTime<Utc>>` ([#1253](https://togithub.com/chronotope/chrono/issues/1253)). Chrono now has a [Discord channel](https://discord.gg/sXpav4PS7M). #### Fixes - Fix arbitrary string slicing in `parse_rfc3339_relaxed` ([#1254](https://togithub.com/chronotope/chrono/issues/1254)) #### Deprecations - Deprecate `TimeZone::datetime_from_str` ([#1251](https://togithub.com/chronotope/chrono/issues/1251)) #### Documentation - Correct documentation for `FromStr` for `Weekday` and `Month` ([#1226](https://togithub.com/chronotope/chrono/issues/1226), thanks [@wfraser](https://togithub.com/wfraser)) #### Internal improvements - Revert "add test_issue\_866" ([#1238](https://togithub.com/chronotope/chrono/issues/1238)) - CI: run tests on `i686` and `wasm32-wasi` ([#1237](https://togithub.com/chronotope/chrono/issues/1237)) - CI: Include doctests for code coverage ([#1248](https://togithub.com/chronotope/chrono/issues/1248)) - Move benchmarks to a separate crate ([#1243](https://togithub.com/chronotope/chrono/issues/1243)) This allows us to upgrade the criterion dependency to 5.1 without changing our MSRV. - Add Discord link to README ([#1240](https://togithub.com/chronotope/chrono/issues/1240), backported in [#1256](https://togithub.com/chronotope/chrono/issues/1256)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.28`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.28) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.27...v0.4.28) This release fixes a test failure on 32-bit targets introduced with 0.4.27, see [https://github.com/chronotope/chrono/issues/1234](https://togithub.com/chronotope/chrono/issues/1234). ### [`v0.4.27`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.27) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.26...v0.4.27) This release bumps the MSRV from 1.56 to 1.57. This allows us to take advantage of the panicking in const feature. In this release most methods on `NaiveDate` and `NaiveTime` are made const, `NaiveDateTime` and others will follow in a later release. The parser for the `%+` formatting specifier and the `RFC3339` formatting item is switched from a strict to a relaxed parser (see [https://github.com/chronotope/chrono/pull/1145](https://togithub.com/chronotope/chrono/pull/1145)). This matches the existing documentation, and the parser used by `DateTime::from_str`. If you need to validate the input, consider using `DateTime::from_rfc3339`. #### Deprecations - Deprecate `DateTime::{from_local, from_utc}` ([https://github.com/chronotope/chrono/pull/1175](https://togithub.com/chronotope/chrono/pull/1175)) #### Additions - Let `DateTime::signed_duration_since` take argument with `Borrow` ([https://github.com/chronotope/chrono/pull/1119](https://togithub.com/chronotope/chrono/pull/1119)) - Implement `PartialOrd` for `Month` ([https://github.com/chronotope/chrono/pull/999](https://togithub.com/chronotope/chrono/pull/999), thanks [@Munksgaard](https://togithub.com/Munksgaard)) - Add `Ord` and `Eq` for types which already derive `PartialOrd` and `PartialEq` ([https://github.com/chronotope/chrono/pull/1128](https://togithub.com/chronotope/chrono/pull/1128), thanks [@totikom](https://togithub.com/totikom)) - implement `FusedIterator` for `NaiveDateDaysIterator` and `NaiveDateWeeksIterator` ([https://github.com/chronotope/chrono/pull/1134](https://togithub.com/chronotope/chrono/pull/1134)) - Make `NaiveDateDaysIterator` and `NaiveDateWeeksIterator` public ([https://github.com/chronotope/chrono/pull/1134](https://togithub.com/chronotope/chrono/pull/1134)) - Add `FromStr` for `FixedOffset` ([https://github.com/chronotope/chrono/pull/1157](https://togithub.com/chronotope/chrono/pull/1157), thanks [@mcronce](https://togithub.com/mcronce)) - Remove `Tz::Offset: Display` requirement from `DateTime::to_rfc*` ([https://github.com/chronotope/chrono/pull/1160](https://togithub.com/chronotope/chrono/pull/1160)) - More flexible offset formatting (not exposed yet) ([https://github.com/chronotope/chrono/pull/1160](https://togithub.com/chronotope/chrono/pull/1160)) - Make `StrftimeItems` with `unstable-locales` work without allocating ([https://github.com/chronotope/chrono/pull/1152](https://togithub.com/chronotope/chrono/pull/1152)) - Make `NaiveDate::from_ymd_opt` const ([https://github.com/chronotope/chrono/pull/1172](https://togithub.com/chronotope/chrono/pull/1172), thanks [@kamadorueda](https://togithub.com/kamadorueda)) - Implement `Error` trait for `ParseWeekdayError` and `ParseMonthError` ([https://github.com/chronotope/chrono/pull/539](https://togithub.com/chronotope/chrono/pull/539), thanks [@mike-kfed](https://togithub.com/mike-kfed)) - Make methods on `NaiveTime` const, update MSRV to 1.57 ([https://github.com/chronotope/chrono/pull/1080](https://togithub.com/chronotope/chrono/pull/1080)) - Make methods on `NaiveDate` const ([https://github.com/chronotope/chrono/pull/1205](https://togithub.com/chronotope/chrono/pull/1205)) - Implement operations for `core::time::Duration` on `DateTime` types ([https://github.com/chronotope/chrono/pull/1229](https://togithub.com/chronotope/chrono/pull/1229)) #### Fixes - Ensure `timestamp_nanos` panics on overflow in release builds ([https://github.com/chronotope/chrono/pull/1123](https://togithub.com/chronotope/chrono/pull/1123)) - Fix `offset_from_local_datetime` for `wasm_bindgen` ([https://github.com/chronotope/chrono/pull/1131](https://togithub.com/chronotope/chrono/pull/1131)) - Parsing: Consider `%s` to be a timestamp in UTC ([https://github.com/chronotope/chrono/pull/1136](https://togithub.com/chronotope/chrono/pull/1136)) - Don't panic when formatting with `%#z` ([https://github.com/chronotope/chrono/pull/1140](https://togithub.com/chronotope/chrono/pull/1140), thanks [@domodwyer](https://togithub.com/domodwyer)) - Parsing: allow MINUS SIGN (U+2212) in offset ([https://github.com/chronotope/chrono/pull/1087](https://togithub.com/chronotope/chrono/pull/1087), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - Fix locale formatting for `%c` and `%r` ([https://github.com/chronotope/chrono/pull/1165](https://togithub.com/chronotope/chrono/pull/1165)) - Localize decimal point with `unstable-locales` feature ([https://github.com/chronotope/chrono/pull/1168](https://togithub.com/chronotope/chrono/pull/1168)) - Fix panic on macOS 10.12 caused by using version 1 of the TZif file format ([https://github.com/chronotope/chrono/pull/1201](https://togithub.com/chronotope/chrono/pull/1201), thanks to help from [@jfro](https://togithub.com/jfro)) - Fix deserialization of negative timestamps ([https://github.com/chronotope/chrono/pull/1194](https://togithub.com/chronotope/chrono/pull/1194)) - Do not use `Offset`'s `Debug` impl when serializing `DateTime` ([https://github.com/chronotope/chrono/pull/1035](https://togithub.com/chronotope/chrono/pull/1035)) - Allow missing seconds in `NaiveTime::from_str` ([https://github.com/chronotope/chrono/pull/1181](https://togithub.com/chronotope/chrono/pull/1181)) - Do not depend on `android-tzdata` if the `clock` feature is not enabled ([https://github.com/chronotope/chrono/pull/1220](https://togithub.com/chronotope/chrono/pull/1220), thanks [@AlexTMjugador](https://togithub.com/AlexTMjugador)) - Small fixes to the RFC 3339 parsers ([https://github.com/chronotope/chrono/pull/1145](https://togithub.com/chronotope/chrono/pull/1145)) #### Documentation - Add "Errors" and "Panics" sections to API docs ([https://github.com/chronotope/chrono/pull/1120](https://togithub.com/chronotope/chrono/pull/1120)) - Specify licenses in SPDX format ([https://github.com/chronotope/chrono/pull/1132](https://togithub.com/chronotope/chrono/pull/1132), backport of [https://github.com/chronotope/chrono/issues/910](https://togithub.com/chronotope/chrono/issues/910), thanks [@LingMan](https://togithub.com/LingMan)) - Fix `NaiveTime` doc typo ([https://github.com/chronotope/chrono/pull/1146](https://togithub.com/chronotope/chrono/pull/1146), thanks [@zachs18](https://togithub.com/zachs18)) - Clarify nanosecond formatting specifier doc ([https://github.com/chronotope/chrono/pull/1173](https://togithub.com/chronotope/chrono/pull/1173)) - Add warning against combining multiple `Datelike::with_*` ([https://github.com/chronotope/chrono/pull/1199](https://togithub.com/chronotope/chrono/pull/1199)) - Fix typo "accepted" ([https://github.com/chronotope/chrono/pull/1209](https://togithub.com/chronotope/chrono/pull/1209), thanks [@simon04](https://togithub.com/simon04)) - Add some examples to `Utc::now` and `Local::now` ([https://github.com/chronotope/chrono/pull/1192](https://togithub.com/chronotope/chrono/pull/1192)) - Add example to `Weekday::num_days_from_monday` ([https://github.com/chronotope/chrono/pull/1193](https://togithub.com/chronotope/chrono/pull/1193)) - Fix some comments and panic messages ([https://github.com/chronotope/chrono/pull/1221](https://togithub.com/chronotope/chrono/pull/1221), thanks [@umanwizard](https://togithub.com/umanwizard)) #### Internal improvements - `DateTime::to_rfc_*` optimizations ([https://github.com/chronotope/chrono/pull/1200](https://togithub.com/chronotope/chrono/pull/1200)) - Move all tests into modules, fix clippy warnings ([https://github.com/chronotope/chrono/pull/1138](https://togithub.com/chronotope/chrono/pull/1138)) - Offset parsing cleanup ([https://github.com/chronotope/chrono/pull/1158](https://togithub.com/chronotope/chrono/pull/1158)) - Factor out formatting to `format/formatting.rs` ([https://github.com/chronotope/chrono/pull/1156](https://togithub.com/chronotope/chrono/pull/1156)) - Format refactorings ([https://github.com/chronotope/chrono/pull/1198](https://togithub.com/chronotope/chrono/pull/1198)) - Format toml files with taplo ([https://github.com/chronotope/chrono/pull/1117](https://togithub.com/chronotope/chrono/pull/1117), thanks [@tottoto](https://togithub.com/tottoto)) - Stop vendoring `saturating_abs` ([https://github.com/chronotope/chrono/pull/1124](https://togithub.com/chronotope/chrono/pull/1124)) - CI: shell set -eux, use bash ([https://github.com/chronotope/chrono/pull/1103](https://togithub.com/chronotope/chrono/pull/1103), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - Fix dead code error when running dateutils test on Windows ([https://github.com/chronotope/chrono/pull/1125](https://togithub.com/chronotope/chrono/pull/1125)) - Remove `Makefile` ([https://github.com/chronotope/chrono/pull/1133](https://togithub.com/chronotope/chrono/pull/1133)) - CI: Test `wasm-bindgen` feature ([https://github.com/chronotope/chrono/pull/1131](https://togithub.com/chronotope/chrono/pull/1131)) - Stop using deprecated methods in parse module ([https://github.com/chronotope/chrono/pull/1142](https://togithub.com/chronotope/chrono/pull/1142)) - Add formatting benchmarks ([https://github.com/chronotope/chrono/pull/1155](https://togithub.com/chronotope/chrono/pull/1155)) - Feature gate tests instead of methods ([https://github.com/chronotope/chrono/pull/1159](https://togithub.com/chronotope/chrono/pull/1159), [https://github.com/chronotope/chrono/pull/1162](https://togithub.com/chronotope/chrono/pull/1162)) - Parallelize `try_verify_against_date_command` ([https://github.com/chronotope/chrono/pull/1161](https://togithub.com/chronotope/chrono/pull/1161)) - CI: also run integration tests with `no_std` ([https://github.com/chronotope/chrono/pull/1166](https://togithub.com/chronotope/chrono/pull/1166)) - Split ` test_parse ` ([https://github.com/chronotope/chrono/pull/1170](https://togithub.com/chronotope/chrono/pull/1170)) - Remove `#![deny(dead_code)]` ([https://github.com/chronotope/chrono/pull/1187](https://togithub.com/chronotope/chrono/pull/1187)) - Clippy fixes for Rust 1.71 ([https://github.com/chronotope/chrono/pull/1186](https://togithub.com/chronotope/chrono/pull/1186)) - Various small improvements ([https://github.com/chronotope/chrono/pull/1191](https://togithub.com/chronotope/chrono/pull/1191)) - Add unit test for uncovered regions ([https://github.com/chronotope/chrono/pull/1149](https://togithub.com/chronotope/chrono/pull/1149), thanks [@CXWorks](https://togithub.com/CXWorks)) - Don't test the same thing twice in `test_date_extreme_offset` ([https://github.com/chronotope/chrono/pull/1195](https://togithub.com/chronotope/chrono/pull/1195)) - CI: Add workflow code coverage report and upload ([https://github.com/chronotope/chrono/pull/1178](https://togithub.com/chronotope/chrono/pull/1178), [https://github.com/chronotope/chrono/pull/1215](https://togithub.com/chronotope/chrono/pull/1215), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - CI: fail on warnings in `features-check` ([https://github.com/chronotope/chrono/pull/1216](https://togithub.com/chronotope/chrono/pull/1216)) - Switch to windows-bindgen ([https://github.com/chronotope/chrono/pull/1202](https://togithub.com/chronotope/chrono/pull/1202), thanks to help from [@MarijnS95](https://togithub.com/MarijnS95)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.26`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.26) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.25...v0.4.26) The changes from [#807](https://togithub.com/chronotope/chrono/issues/807) we merged for 0.4.25 unfortunately restricted parsing in a way that was incompatible with earlier 0.4.x releases. We reverted this in [#1113](https://togithub.com/chronotope/chrono/issues/1113). A small amount of other changes were merged since. - Update README ([#1111](https://togithub.com/chronotope/chrono/issues/1111), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Revert backport of [#807](https://togithub.com/chronotope/chrono/issues/807) ([#1113](https://togithub.com/chronotope/chrono/issues/1113), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Update to 2021 edition ([#1109](https://togithub.com/chronotope/chrono/issues/1109), thanks to [@tottoto](https://togithub.com/tottoto)) - Fix `DurationRound` panics from issue [#1010](https://togithub.com/chronotope/chrono/issues/1010) ([#1093](https://togithub.com/chronotope/chrono/issues/1093), thanks to [@pitdicker](https://togithub.com/pitdicker)) - tests: date path consolidate (branch 0.4.x) ([#1090](https://togithub.com/chronotope/chrono/issues/1090), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - Parse tests nanosecond bare dot (branch 0.4.x) ([#1098](https://togithub.com/chronotope/chrono/issues/1098), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - yamllint cleanup lint.yml test.yml ([#1102](https://togithub.com/chronotope/chrono/issues/1102), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - Remove num-iter dependency ([#1107](https://togithub.com/chronotope/chrono/issues/1107), thanks to [@tottoto](https://togithub.com/tottoto)) Thanks on behalf of the chrono team ([@djc](https://togithub.com/djc) and [@esheppa](https://togithub.com/esheppa)) to all contributors! ### [`v0.4.25`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.25) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.24...v0.4.25) Time for another maintenance release. This release bumps the MSRV to 1.56; given MSRV bumps in chrono's dependencies (notably for syn 2), we felt that it no longer made sense to support any older versions. Feedback welcome in our issue tracker! #### Additions - Bump the MSRV to 1.56 ([#1053](https://togithub.com/chronotope/chrono/issues/1053)) - Apply comments from MSRV bump ([#1026](https://togithub.com/chronotope/chrono/issues/1026), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Remove num-integer dependency ([#1037](https://togithub.com/chronotope/chrono/issues/1037), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `NaiveDateTime::and_utc()` method ([#952](https://togithub.com/chronotope/chrono/issues/952), thanks to [@klnusbaum](https://togithub.com/klnusbaum)) - derive `Hash` for most pub types that also derive `PartialEq` ([#938](https://togithub.com/chronotope/chrono/issues/938), thanks to [@bruceg](https://togithub.com/bruceg)) - Add `parse_and_remainder()` methods ([#1011](https://togithub.com/chronotope/chrono/issues/1011), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `DateTime::fix_offset()` ([#1030](https://togithub.com/chronotope/chrono/issues/1030), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `#[track_caller]` to `LocalResult::unwrap` ([#1046](https://togithub.com/chronotope/chrono/issues/1046), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `#[must_use]` to some methods ([#1007](https://togithub.com/chronotope/chrono/issues/1007), thanks to [@aceArt-GmbH](https://togithub.com/aceArt-GmbH)) - Implement `PartialOrd` for `Month` ([#999](https://togithub.com/chronotope/chrono/issues/999), thanks to [@Munksgaard](https://togithub.com/Munksgaard)) - Add `impl From<NaiveDateTime> for NaiveDate` ([#1012](https://togithub.com/chronotope/chrono/issues/1012), thanks to [@pezcore](https://togithub.com/pezcore)) - Extract timezone info from tzdata file on Android ([#978](https://togithub.com/chronotope/chrono/issues/978), thanks to [@RumovZ](https://togithub.com/RumovZ)) #### Fixes - Prevent string slicing inside char boundaries ([#1024](https://togithub.com/chronotope/chrono/issues/1024), thanks to [@pitdicker](https://togithub.com/pitdicker)) - fix IsoWeek so that its flags are always correct ([#991](https://togithub.com/chronotope/chrono/issues/991), thanks to [@moshevds](https://togithub.com/moshevds)) - Fix out-of-range panic in `NaiveWeek::last_day` ([#1070](https://togithub.com/chronotope/chrono/issues/1070), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Use correct offset in conversion from `Local` to `FixedOffset` ([#1041](https://togithub.com/chronotope/chrono/issues/1041), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix military timezones in RFC 2822 parsing ([#1013](https://togithub.com/chronotope/chrono/issues/1013), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Guard against overflow in NaiveDate::with_\*0 methods ([#1023](https://togithub.com/chronotope/chrono/issues/1023), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix panic in from_num_days_from_ce_opt ([#1052](https://togithub.com/chronotope/chrono/issues/1052), thanks to [@pitdicker](https://togithub.com/pitdicker)) #### Refactoring - Rely on std for getting local time offset ([#1072](https://togithub.com/chronotope/chrono/issues/1072), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Make functions in internals const ([#1043](https://togithub.com/chronotope/chrono/issues/1043), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Refactor windows module in `Local` ([#992](https://togithub.com/chronotope/chrono/issues/992), thanks to [@nekevss](https://togithub.com/nekevss)) - Simplify from_timestamp_millis, from_timestamp_micros ([#1032](https://togithub.com/chronotope/chrono/issues/1032), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Backport [#983](https://togithub.com/chronotope/chrono/issues/983) and [#1000](https://togithub.com/chronotope/chrono/issues/1000) ([#1063](https://togithub.com/chronotope/chrono/issues/1063), thanks to [@pitdicker](https://togithub.com/pitdicker)) #### Documentation - Backport documentation improvements ([#1066](https://togithub.com/chronotope/chrono/issues/1066), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add documentation for %Z quirk ([#1051](https://togithub.com/chronotope/chrono/issues/1051), thanks to [@campbellcole](https://togithub.com/campbellcole)) - Add an example to Weekday ([#1019](https://togithub.com/chronotope/chrono/issues/1019), thanks to [@pitdicker](https://togithub.com/pitdicker)) #### Internal improvements - Gate test on `clock` feature ([#1061](https://togithub.com/chronotope/chrono/issues/1061), thanks to [@pitdicker](https://togithub.com/pitdicker)) - CI: Also run tests with `--no-default-features` ([#1059](https://togithub.com/chronotope/chrono/issues/1059), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Prevent `bench_year_flags_from_year` from being optimized out ([#1034](https://togithub.com/chronotope/chrono/issues/1034), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix test_leap_second during DST transition ([#1064](https://togithub.com/chronotope/chrono/issues/1064), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix warnings when running tests on Windows ([#1038](https://togithub.com/chronotope/chrono/issues/1038), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix tests on AIX ([#1028](https://togithub.com/chronotope/chrono/issues/1028), thanks to [@ecnelises](https://togithub.com/ecnelises)) - Fix doctest warnings, remove mention of deprecated methods from main doc ([#1081](https://togithub.com/chronotope/chrono/issues/1081), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Reformat `test_datetime_parse_from_str` ([#1078](https://togithub.com/chronotope/chrono/issues/1078), thanks to [@pitdicker](https://togithub.com/pitdicker)) - GitHub yml shell `set -eux`, use bash ([#1103](https://togithub.com/chronotope/chrono/issues/1103), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - test: explicitly set `LANG` to `c` in gnu `date` ([#1089](https://togithub.com/chronotope/chrono/issues/1089), thanks to [@scarf005](https://togithub.com/scarf005)) - Switch test to `TryFrom` ([#1086](https://togithub.com/chronotope/chrono/issues/1086), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add test for issue 551 ([#1020](https://togithub.com/chronotope/chrono/issues/1020), thanks to [@pitdicker](https://togithub.co </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/X-oss-byte/Canary-nextjs).

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [chrono](https://togithub.com/chronotope/chrono) | dependencies | patch | `0.4` -> `0.4.38` | --- ### Release Notes <details> <summary>chronotope/chrono (chrono)</summary> ### [`v0.4.38`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.38) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.37...v0.4.38) This release bring a ca. 20% improvement to the performance of the formatting code, and a convenient `days_since` method for the `Weekday` type. Chrono 0.4.38 also removes the long deprecated `rustc-serialize` feature. Support for `rustc-serialize` will be [soft-destabilized in the next Rust edition](https://togithub.com/rust-lang/rust/pull/116016). Removing the feature will not break existing users of the feature; Cargo will just not update dependents that rely on it to newer versions of chrono. In chrono 0.4.36 we made an accidental breaking change by switching to `derive(Copy)` for `DateTime` instead of a manual implementation. It is reverted in this release. ### Removals - Remove `rustc-serialize` feature ([#1548](https://togithub.com/chronotope/chrono/issues/1548), thanks [@workingjubilee](https://togithub.com/workingjubilee)) ### Additions - Add `Weekday::days_since` ([#1249](https://togithub.com/chronotope/chrono/issues/1249), based on [#216](https://togithub.com/chronotope/chrono/issues/216) by [@clarfonthey](https://togithub.com/clarfonthey)) - Add `TimeDelta::checked_mul` and `TimeDelta::checked_div` ([#1565](https://togithub.com/chronotope/chrono/issues/1565), thanks [@Zomtir](https://togithub.com/Zomtir)) ### Fixes - Return error when rounding with a zero duration ([#1474](https://togithub.com/chronotope/chrono/issues/1474), thanks [@Dav1dde](https://togithub.com/Dav1dde)) - Manually implement `Copy` for `DateTime` if offset is `Copy` ([#1573](https://togithub.com/chronotope/chrono/issues/1573)) ### Internal - Inline `test_encodable_json` and `test_decodable_json` functions ([#1550](https://togithub.com/chronotope/chrono/issues/1550)) - CI: Reduce combinations in `cargo hack check` ([#1553](https://togithub.com/chronotope/chrono/issues/1553)) - Refactor formatting code ([#1335](https://togithub.com/chronotope/chrono/issues/1335)) - Optimize number formatting ([#1558](https://togithub.com/chronotope/chrono/issues/1558)) - Only package files needed for building and testing ([#1554](https://togithub.com/chronotope/chrono/issues/1554)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.37`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.37) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.36...v0.4.37) Version 0.4.36 introduced an unexpected breaking change and was yanked. In it `LocalResult` was renamed to `MappedLocalTime` to avoid the impression that it is a `Result` type were some of the results are errors. For backwards compatibility a type alias with the old name was added. As it turns out there is one case where a type alias behaves differently from the regular enum: you can't import enum variants from a type alias with `use chrono::LocalResult::*`. With 0.4.37 we make the new name `MappedLocalTime` the alias, but keep using it in function signatures and the documentation as much as possible. See also the release notes of [chrono 0.4.36](https://togithub.com/chronotope/chrono/releases/tag/v0.4.36) from yesterday for the yanked release. ### [`v0.4.36`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.36) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.35...v0.4.36) This release un-deprecates the methods on `TimeDelta` that were deprecated with the 0.4.35 release because of the churn they are causing for the ecosystem. New is the `DateTime::with_time()` method. As an example of when it is useful: ```rust use chrono::{Local, NaiveTime}; // Today at 12:00:00 let today_noon = Local::now().with_time(NaiveTime::from_hms_opt(12, 0, 0).unwrap()); ``` ### Additions - Add `DateTime::with_time()` ([#1510](https://togithub.com/chronotope/chrono/issues/1510)) ### Deprecations - Revert `TimeDelta` deprecations ([#1543](https://togithub.com/chronotope/chrono/issues/1543)) - Deprecate `TimeStamp::timestamp_subsec_nanos`, which was missed in the 0.4.35 release ([#1486](https://togithub.com/chronotope/chrono/issues/1486)) ### Documentation - Correct version number of deprecation notices ([#1486](https://togithub.com/chronotope/chrono/issues/1486)) - Fix some typos ([#1505](https://togithub.com/chronotope/chrono/issues/1505)) - Slightly improve serde documentation ([#1519](https://togithub.com/chronotope/chrono/issues/1519)) - Main documentation: simplify links and reflow text ([#1535](https://togithub.com/chronotope/chrono/issues/1535)) ### Internal - CI: Lint benchmarks ([#1489](https://togithub.com/chronotope/chrono/issues/1489)) - Remove unnessary `Copy` and `Send` impls ([#1492](https://togithub.com/chronotope/chrono/issues/1492), thanks [@erickt](https://togithub.com/erickt)) - Backport streamlined `NaiveDate` unit tests ([#1500](https://togithub.com/chronotope/chrono/issues/1500), thanks [@Zomtir](https://togithub.com/Zomtir)) - Rename `LocalResult` to `TzResolution`, add alias ([#1501](https://togithub.com/chronotope/chrono/issues/1501)) - Update windows-bindgen to 0.55 ([#1504](https://togithub.com/chronotope/chrono/issues/1504)) - Avoid duplicate imports, which generate warnings on nightly ([#1507](https://togithub.com/chronotope/chrono/issues/1507)) - Add extra debug assertions to `NaiveDate::from_yof` ([#1518](https://togithub.com/chronotope/chrono/issues/1518)) - Some small simplifications to `DateTime::date_naive` and `NaiveDate::diff_months` ([#1530](https://togithub.com/chronotope/chrono/issues/1530)) - Remove `unwrap` in Unix `Local` type ([#1533](https://togithub.com/chronotope/chrono/issues/1533)) - Use different method to ignore feature-dependent doctests ([#1534](https://togithub.com/chronotope/chrono/issues/1534)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.35`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.35) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.34...v0.4.35) Most of our efforts have shifted to improving the API for a 0.5 release, for which cleanups and refactorings are landing on the 0.4.x branch. The most significant changes in this release are two sets of deprecations. - We deprecated all timestamp-related methods on `NaiveDateTime`. The reason is that a timestamp is defined to be in UTC. The `NaiveDateTime` type doesn't know the offset from UTC, so it was technically wrong to have these methods. The alternative is to use the similar methods on the `DateTime<Utc>` type, or from the `TimeZone` trait. Converting from `NaiveDateTime` to `DateTime<Utc>` is simple with `.and_utc()`, and in the other direction with `.naive_utc()`. - The panicking constructors of `TimeDelta` (the new name of the `Duration` type) are deprecated. This was the last part of chrono that defaulted to panicking on error, dating from before rust 1.0. - A nice change is that `NaiveDate` now includes a niche. So now `Option<NaiveDate>`, `Option<NaiveDateTime>` and `Option<DateTime<Tz>>` are the same size as their base types. - `format::Numeric` and `format::Fixed` are marked as `non_exhaustive`. This will allow us to improve our formatting and parsing support, and we have reason to believe this breaking change will have little to no impact on users. ### Additions - Add `DateTime::{from_timestamp_micros, from_timestamp_nanos}` ([#1234](https://togithub.com/chronotope/chrono/issues/1234)) - Add getters to `Parsed` ([#1465](https://togithub.com/chronotope/chrono/issues/1465)) ### Deprecations - Deprecate timestamp methods on `NaiveDateTime` ([#1473](https://togithub.com/chronotope/chrono/issues/1473)) - Deprecate panicking constructors of `TimeDelta` ([#1450](https://togithub.com/chronotope/chrono/issues/1450)) ### Changes/fixes - Use `NonZeroI32` inside `NaiveDate` ([#1207](https://togithub.com/chronotope/chrono/issues/1207)) - Mark `format::Numeric` and `format::Fixed` as `non_exhaustive` ([#1430](https://togithub.com/chronotope/chrono/issues/1430)) - `Parsed` fixes to error values ([#1439](https://togithub.com/chronotope/chrono/issues/1439)) - Use `overflowing_naive_local` in `DateTime::checked_add*` ([#1333](https://togithub.com/chronotope/chrono/issues/1333)) - Do complete range checks in `Parsed::set_*` ([#1465](https://togithub.com/chronotope/chrono/issues/1465)) ### Documentation - Rustfmt doctests ([#1452](https://togithub.com/chronotope/chrono/issues/1452)) - Improve docs for crate features ([#1455](https://togithub.com/chronotope/chrono/issues/1455), thanks [@edmorley](https://togithub.com/edmorley)) - Add more documentation and examples to `Parsed` ([#1439](https://togithub.com/chronotope/chrono/issues/1439)) ### Internal - Refactor `internals` module ([#1428](https://togithub.com/chronotope/chrono/issues/1428), [#1429](https://togithub.com/chronotope/chrono/issues/1429), [#1431](https://togithub.com/chronotope/chrono/issues/1431), [#1432](https://togithub.com/chronotope/chrono/issues/1432), [#1433](https://togithub.com/chronotope/chrono/issues/1433), [#1438](https://togithub.com/chronotope/chrono/issues/1438)) - CI: test cross-compiling to `x86_64-unknown-illumos` instead of Solaris ([#1437](https://togithub.com/chronotope/chrono/issues/1437)) - CI: lint Windows target, fix clippy warning ([#1441](https://togithub.com/chronotope/chrono/issues/1441)) - CI: only run `cargo hack check` on Linux ([#1442](https://togithub.com/chronotope/chrono/issues/1442)) - Update windows-bindgen to 0.54 ([#1462](https://togithub.com/chronotope/chrono/issues/1462), [#1483](https://togithub.com/chronotope/chrono/issues/1483)) - Simplify error value of `parse_internal` ([#1459](https://togithub.com/chronotope/chrono/issues/1459)) - Simplify `SerdeError` ([#1458](https://togithub.com/chronotope/chrono/issues/1458)) - Simplify `NaiveDate::from_isoywd` a bit ([#1464](https://togithub.com/chronotope/chrono/issues/1464)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.34`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.34) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.33...v0.4.34) ### Notable changes - In chrono 0.4.34 we finished the work to make all methods const where doing so is supported by rust 1.61. - We renamed the `Duration` type to `TimeDelta`. This removes the confusion between chrono's type and the later `Duration` type in the standard library. It will remain available under the old name as a type alias for compatibility. - The Windows implementation of `Local` is rewritten. The new version avoids panics when the date is outside of the range supported by windows (the years 1601 to 30828), and gives more accurate results during DST transitions. - The `Display` format of `TimeDelta` is modified to conform better to ISO 8601. Previously it converted all values greater than 24 hours to a value with days. This is not correct, as doing so changes the duration from an 'accurate' to a 'nominal' representation to use ISO 8601 terms. ### Fixes - Add missing range check in `TimeDelta::milliseconds` ([#1385](https://togithub.com/chronotope/chrono/issues/1385), thanks [@danwilliams](https://togithub.com/danwilliams)) - Remove check for `DurationExceedsTimestamp` in `DurationRound` ([#1403](https://togithub.com/chronotope/chrono/issues/1403), thanks [@joroKr21](https://togithub.com/joroKr21)) - Fix localized formatting with `%X` ([https://github.com/chronotope/pure-rust-locales/pull/12](https://togithub.com/chronotope/pure-rust-locales/pull/12), [#1420](https://togithub.com/chronotope/chrono/issues/1420)) - Windows: base implementation on `GetTimeZoneInformationForYear` ([#1017](https://togithub.com/chronotope/chrono/issues/1017)) ### Additions - Add `TimeDelta::try_milliseconds` ([#1385](https://togithub.com/chronotope/chrono/issues/1385), thanks [@danwilliams](https://togithub.com/danwilliams)) - Add `TimeDelta::new` ([#1337](https://togithub.com/chronotope/chrono/issues/1337)) - Add `StrftimeItems::{parse, parse_to_owned}` and more documentation ([#1184](https://togithub.com/chronotope/chrono/issues/1184)) - More standard traits and documentation for `format::Locale` (via [https://github.com/chronotope/pure-rust-locales/pull/8](https://togithub.com/chronotope/pure-rust-locales/pull/8)) ### Changes - Rename `Duration` to `TimeDelta`, add type alias ([#1406](https://togithub.com/chronotope/chrono/issues/1406)) - Make `TimeDelta` methods const ([#1337](https://togithub.com/chronotope/chrono/issues/1337)) - Make remaining methods of `NaiveDate`, `NaiveWeek`, `NaiveTime` and `NaiveDateTime` const where possible ([#1337](https://togithub.com/chronotope/chrono/issues/1337)) - Make methods on `DateTime` const where possible ([#1400](https://togithub.com/chronotope/chrono/issues/1400)) - Make `Display` format of `TimeDelta` conform better to ISO 8601 ([#1328](https://togithub.com/chronotope/chrono/issues/1328)) ### Documentation - Fix the formatting of `timestamp_micros`'s Example doc ([#1338](https://togithub.com/chronotope/chrono/issues/1338) via [#1386](https://togithub.com/chronotope/chrono/issues/1386), thanks [@emikitas](https://togithub.com/emikitas)) - Specify branch for GitHub Actions badge and fix link ([#1388](https://togithub.com/chronotope/chrono/issues/1388)) - Don't mention some deprecated methods in docs ([#1395](https://togithub.com/chronotope/chrono/issues/1395)) - Remove stray documentation from main ([#1397](https://togithub.com/chronotope/chrono/issues/1397)) - Improved documentation of `TimeDelta` constructors ([#1385](https://togithub.com/chronotope/chrono/issues/1385), thanks [@danwilliams](https://togithub.com/danwilliams)) ### Internal - Switch branch names: 0.4.x releases are the `main` branch, work on 0.5 happens in the `0.5.x` branch ([#1390](https://togithub.com/chronotope/chrono/issues/1390), [#1402](https://togithub.com/chronotope/chrono/issues/1402)). - Don't use deprecated method in `impl Arbitrary for DateTime` and set up CI test ([#1336](https://togithub.com/chronotope/chrono/issues/1336)) - Remove workaround for Rust < 1.61 ([#1393](https://togithub.com/chronotope/chrono/issues/1393)) - Bump `codecov/codecov-action` from 3 to 4 ([#1404](https://togithub.com/chronotope/chrono/issues/1404)) - Remove partial support for handling `-0000` offset ([#1411](https://togithub.com/chronotope/chrono/issues/1411)) - Move `TOO_LONG` error out of `parse_internal` ([#1419](https://togithub.com/chronotope/chrono/issues/1419)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.33`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.33) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.32...v0.4.33) This release fixes the broken docrs.rs build of [chrono 0.4.32](https://togithub.com/chronotope/chrono/releases/tag/v0.4.32). #### What's Changed - Make `rkyv` feature imply `size_32` ([#1383](https://togithub.com/chronotope/chrono/issues/1383)) - Fixed typo in `Duration::hours()` exception ([#1384](https://togithub.com/chronotope/chrono/issues/1384), thanks [@danwilliams](https://togithub.com/danwilliams)) ### [`v0.4.32`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.32) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.31...v0.4.32) In this release we shipped part of the effort to reduce the number of methods that could unexpectedly panic, notably for the `DateTime` and `Duration` types. Chrono internally stores the value of a `DateTime` in UTC, and transparently converts it to the local value as required. For example adding a second to a `DateTime` needs to be done in UTC to get the correct result, but adding a day needs to be done in local time to be correct. What happens when the value is near the edge of the representable range, and the implicit conversions pushes it beyond the representable range? *Many* methods could panic on such inputs, including formatting the value for `Debug` output. In chrono 0.4.32 the range of `NaiveDate`, `NaiveDateTime` and `DateTime` is made slightly smaller. This allows us to always do the implicit conversion, and in many cases return the expected result. Specifically the range is now from January 1, -262144 until December 31, 262143, one year less on both sides than before. We expect this may trip up tests if you hardcoded the `MIN` and `MAX` dates. `Duration` had a similar issue. The range of this type was pretty arbitrary picked to match the range of an `i64` in milliseconds. Negating an `i64::MIN` pushes a value out of range, and in the same way negating `Duration::MIN` could push it out of our defined range and cause a panic. This turns out to be somewhat common and hidden behind many layers of abstraction. We adjusted the type to have a minimum value of `-Duration::MAX` instead and prevent the panic case. Other highlights: - `Duration` gained new fallible initialization methods. - Better support for `rkyv`. - Most methods on `NaiveDateTime` are now const. - We had to bump our MSRV to 1.61 to keep building with our dependencies. This will also allow us to make more methods on `DateTime` const in a future release. Complete list of changes: #### Fixes - Fix panic in `TimeZone::from_local_datetime` ([#1071](https://togithub.com/chronotope/chrono/issues/1071)) - Fix out of range panics in `DateTime` getters and setters ([#1317](https://togithub.com/chronotope/chrono/issues/1317), [#1329](https://togithub.com/chronotope/chrono/issues/1329)) #### Additions - Add `NaiveDateTime::checked_(add|sub)_offset` ([#1313](https://togithub.com/chronotope/chrono/issues/1313)) - Add `DateTime::to_utc` ([#1325](https://togithub.com/chronotope/chrono/issues/1325)) - Derive `Default` for `Duration` ([#1327](https://togithub.com/chronotope/chrono/issues/1327)) - Add `Duration::subsec_nanos` ([#1327](https://togithub.com/chronotope/chrono/issues/1327)) - Add `try_*` builders to `Duration` ([#1327](https://togithub.com/chronotope/chrono/issues/1327)) - Implement `AddAssign` and `SubAssign` for `Duration` ([#1327](https://togithub.com/chronotope/chrono/issues/1327)) - Make methods on `NaiveDateTime` const where possible ([#1286](https://togithub.com/chronotope/chrono/issues/1286)) - Split `clock` feature into `clock` and `now` ([#1343](https://togithub.com/chronotope/chrono/issues/1343), thanks [@mmastrac](https://togithub.com/mmastrac)) - Add `From<NaiveDate>` for `NaiveDateTime` ([#1355](https://togithub.com/chronotope/chrono/issues/1355), thanks [@dcechano](https://togithub.com/dcechano)) - Add `NaiveDateTime::from_timestamp_nanos` ([#1357](https://togithub.com/chronotope/chrono/issues/1357), thanks [@Ali-Mirghasemi](https://togithub.com/Ali-Mirghasemi)) - Add `Months::num_months()` and `num_years()` ([#1373](https://togithub.com/chronotope/chrono/issues/1373), thanks [@danwilliams](https://togithub.com/danwilliams)) - Add `DateTime<Utc>::from_timestamp_millis` ([#1374](https://togithub.com/chronotope/chrono/issues/1374), thanks [@xmakro](https://togithub.com/xmakro)) #### Changes - Fix panic in `Duration::MIN.abs()` (adjust `Duration::MIN` by 1 millisecond) ([#1334](https://togithub.com/chronotope/chrono/issues/1334)) - Bump MSRV to 1.61 ([#1347](https://togithub.com/chronotope/chrono/issues/1347)) - Update windows-targets requirement from 0.48 to 0.52 ([#1360](https://togithub.com/chronotope/chrono/issues/1360)) - Update windows-bindgen to 0.52 ([#1379](https://togithub.com/chronotope/chrono/issues/1379)) #### Deprecations - Deprecate standalone `format` functions ([#1306](https://togithub.com/chronotope/chrono/issues/1306)) #### Documentation - Improve doc comment and tests for timestamp_nanos_opt ([#1299](https://togithub.com/chronotope/chrono/issues/1299), thanks [@mlegner](https://togithub.com/mlegner)) - Switch to `doc_auto_cfg` ([#1305](https://togithub.com/chronotope/chrono/issues/1305), [#1326](https://togithub.com/chronotope/chrono/issues/1326)) - Document panics in `Add`/`Sub` impls and use `expect` ([#1316](https://togithub.com/chronotope/chrono/issues/1316)) - Improve types listed in top-level documentation ([#1274](https://togithub.com/chronotope/chrono/issues/1274)) - Improve deprecation note of `TimeZone::datetime_from_str` ([#1342](https://togithub.com/chronotope/chrono/issues/1342), thanks [@tmccombs](https://togithub.com/tmccombs)) - Fix typos in `Datelike` impl for `DateTime` ([#1376](https://togithub.com/chronotope/chrono/issues/1376), thanks [@ElectrifyPro](https://togithub.com/ElectrifyPro)) #### Rkyv support - Export `Archived*` types in `rkyv` module ([#1304](https://togithub.com/chronotope/chrono/issues/1304)) - Duplicate derives on `Archived*` types ([#1271](https://togithub.com/chronotope/chrono/issues/1271), thanks [@Awpteamoose](https://togithub.com/Awpteamoose)) - Archive derive of PartialEq for rkyv ([#959](https://togithub.com/chronotope/chrono/issues/959), thanks [@mkatychev](https://togithub.com/mkatychev)) - Expose rkyv features as features for chrono users ([#1368](https://togithub.com/chronotope/chrono/issues/1368), thanks [@gz](https://togithub.com/gz)) #### Changes to unstable features - Don't let `unstable-locales` imply the `alloc` feature ([#1307](https://togithub.com/chronotope/chrono/issues/1307)) - Remove `format::{format_localized, format_item_localized}` ([#1311](https://togithub.com/chronotope/chrono/issues/1311)) - Inline `write_rfc2822_inner`, don't localize ([#1322](https://togithub.com/chronotope/chrono/issues/1322)) #### Internal - Add benchmark for `DateTime::with_*` ([#1309](https://togithub.com/chronotope/chrono/issues/1309)) - Fix `*_DAYS_FROM_YEAR_0` calculation ([#1312](https://togithub.com/chronotope/chrono/issues/1312)) - Add `NaiveTime::overflowing_(add|sub)_offset` ([#1310](https://togithub.com/chronotope/chrono/issues/1310)) - Rewrite `DateTime::overflowing_(add|sub)_offset` ([#1069](https://togithub.com/chronotope/chrono/issues/1069)) - Tests calling date command `set env LC_ALL` ([#1315](https://togithub.com/chronotope/chrono/issues/1315), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - Update `deny.toml` ([#1320](https://togithub.com/chronotope/chrono/issues/1320)) - Bump actions/setup-node from 3 to 4 ([#1346](https://togithub.com/chronotope/chrono/issues/1346)) - test.yml remove errant `with: node-version` ([#1352](https://togithub.com/chronotope/chrono/issues/1352), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - CI Linting: Fix missing sources checkout in `toml` job ([#1371](https://togithub.com/chronotope/chrono/issues/1371), thanks [@gibbz00](https://togithub.com/gibbz00)) - Silence clippy lint for test code with Rust 1.74.0 ([#1362](https://togithub.com/chronotope/chrono/issues/1362)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.31`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.31) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.30...v0.4.31) Another maintenance release. It was not a planned effort to improve our support for UNIX timestamps, yet most PRs seem related to this. ##### Deprecations - Deprecate `timestamp_nanos` in favor of the non-panicking `timestamp_nanos_opt` ([#1275](https://togithub.com/chronotope/chrono/issues/1275)) ##### Additions - Add `DateTime::<Utc>::from_timestamp` ([#1279](https://togithub.com/chronotope/chrono/issues/1279), thanks [@demurgos](https://togithub.com/demurgos)) - Add `TimeZone::timestamp_micros` ([#1285](https://togithub.com/chronotope/chrono/issues/1285), thanks [@emikitas](https://togithub.com/emikitas)) - Add `DateTime<Tz>::timestamp_nanos_opt` and `NaiveDateTime::timestamp_nanos_opt` ([#1275](https://togithub.com/chronotope/chrono/issues/1275)) - Add `UNIX_EPOCH` constants ([#1291](https://togithub.com/chronotope/chrono/issues/1291)) ##### Fixes - Format day of month in RFC 2822 without padding ([#1272](https://togithub.com/chronotope/chrono/issues/1272)) - Don't allow strange leap seconds which are not on a minute boundary initialization methods ([#1283](https://togithub.com/chronotope/chrono/issues/1283)) This makes many methods a little more strict: - `NaiveTime::from_hms_milli` - `NaiveTime::from_hms_milli_opt` - `NaiveTime::from_hms_micro` - `NaiveTime::from_hms_micro_opt` - `NaiveTime::from_hms_nano` - `NaiveTime::from_hms_nano_opt` - `NaiveTime::from_num_seconds_from_midnight` - `NaiveTime::from_num_seconds_from_midnight_opt` - `NaiveDate::and_hms_milli` - `NaiveDate::and_hms_milli_opt` - `NaiveDate::and_hms_micro` - `NaiveDate::and_hms_micro_opt` - `NaiveDate::and_hms_nano` - `NaiveDate::and_hms_nano_opt` - `NaiveDateTime::from_timestamp` - `NaiveDateTime::from_timestamp_opt` - `TimeZone::timestamp` - `TimeZone::timestamp_opt` - Fix underflow in `NaiveDateTime::timestamp_nanos_opt` ([#1294](https://togithub.com/chronotope/chrono/issues/1294), thanks [@crepererum](https://togithub.com/crepererum)) ##### Documentation - Add more documentation about the RFC 2822 obsolete date format ([#1267](https://togithub.com/chronotope/chrono/issues/1267)) ##### Internal - Remove internal `__doctest` feature and `doc_comment` dependency ([#1276](https://togithub.com/chronotope/chrono/issues/1276)) - CI: Bump `actions/checkout` from 3 to 4 ([#1280](https://togithub.com/chronotope/chrono/issues/1280)) - Optimize `NaiveDate::add_days` for small values ([#1214](https://togithub.com/chronotope/chrono/issues/1214)) - Upgrade `pure-rust-locales` to 0.7.0 ([#1288](https://togithub.com/chronotope/chrono/issues/1288), thanks [@jeremija](https://togithub.com/jeremija) wo did good improvements on `pure-rust-locales`) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.30`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.30) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.29...v0.4.30) In this release, we have decided to swap out the `chrono::Duration` type (which has been a re-export of time 0.1 `Duration` type) with our own definition, which exposes a strict superset of the `time::Duration` API. This helps avoid warnings about the [CVE-2020-26235] and [RUSTSEC-2020-0071] advisories for downstream users and allows us to improve the `Duration` API going forward. While this is technically a SemVer-breaking change, we expect the risk of downstream users experiencing actual incompatibility to be exceedingly limited (see [our analysis](https://togithub.com/chronotope/chrono/pull/1095#issuecomment-1571716955) of public code using a crater-like experiment), and not enough justification for the large ecosystem churn of a 0.5 release. If you have any feedback on these changes, please let us know in [#1268](https://togithub.com/chronotope/chrono/issues/1268). ##### Additions - Add `NaiveDate::leap_year` ([#1261](https://togithub.com/chronotope/chrono/issues/1261)) ##### Documentation - Update main documentation from README ([#1260](https://togithub.com/chronotope/chrono/issues/1260), thanks [@Stygmates](https://togithub.com/Stygmates)) - Add history of relation between chrono and time 0.1 to documentation ([https://github.com/chronotope/chrono/pull/1264](https://togithub.com/chronotope/chrono/pull/1264), [https://github.com/chronotope/chrono/pull/1266](https://togithub.com/chronotope/chrono/pull/1266)) - Clarify `Timelike::num_seconds_from_midnight` is a simple mapping ([#1255](https://togithub.com/chronotope/chrono/issues/1255)) #### Relation between chrono and time 0.1 Rust first had a `time` module added to `std` in its 0.7 release. It later moved to `libextra`, and then to a `libtime` library shipped alongside the standard library. In 2014 work on chrono started in order to provide a full-featured date and time library in Rust. Some improvements from chrono made it into the standard library; notably, `chrono::Duration` was included as `std::time::Duration` ([rust#15934]) in 2014. In preparation of Rust 1.0 at the end of 2014 `libtime` was moved out of the Rust distro and into the `time` crate to eventually be redesigned ([rust#18832], [rust#18858]), like the `num` and `rand` crates. Of course chrono kept its dependency on this `time` crate. `time` started re-exporting `std::time::Duration` during this period. Later, the standard library was changed to have a more limited unsigned `Duration` type ([rust#24920], [RFC 1040]), while the `time` crate kept the full functionality with `time::Duration`. `time::Duration` had been a part of chrono's public API. By 2016 `time` 0.1 lived under the `rust-lang-deprecated` organisation and was not actively maintained ([time#136]). chrono absorbed the platform functionality and `Duration` type of the `time` crate in [chrono#478] (the work started in [chrono#286]). In order to preserve compatibility with downstream crates depending on `time` and `chrono` sharing a `Duration` type, chrono kept depending on time 0.1. chrono offered the option to opt out of the `time` dependency by disabling the `oldtime` feature (swapping it out for an effectively similar chrono type). In 2019, [@jhpratt](https://togithub.com/jhpratt) took over maintenance on the `time` crate and released what amounts to a new crate as `time` 0.2. [rust#15934]: https://togithub.com/rust-lang/rust/pull/15934 [rust#18832]: https://togithub.com/rust-lang/rust/pull/18832#issuecomment-62448221 [rust#18858]: https://togithub.com/rust-lang/rust/pull/18858 [rust#24920]: https://togithub.com/rust-lang/rust/pull/24920 [RFC 1040]: https://rust-lang.github.io/rfcs/1040-duration-reform.html [time#136]: https://togithub.com/time-rs/time/issues/136 [chrono#286]: https://togithub.com/chronotope/chrono/pull/286 [chrono#478]: https://togithub.com/chronotope/chrono/pull/478 ##### Security advisories In November of 2020 [CVE-2020-26235] and [RUSTSEC-2020-0071] were opened against the `time` crate. [@quininer](https://togithub.com/quininer) had found that calls to `localtime_r` may be unsound ([chrono#499]). Eventually, almost a year later, this was also made into a security advisory against chrono as [RUSTSEC-2020-0159], which had platform code similar to `time`. On Unix-like systems a process is given a timezone id or description via the `TZ` environment variable. We need this timezone data to calculate the current local time from a value that is in UTC, such as the time from the system clock. `time` 0.1 and chrono used the POSIX function `localtime_r` to do the conversion to local time, which reads the `TZ` variable. Rust assumes the environment to be writable and uses locks to access it from multiple threads. Some other programming languages and libraries use similar locking strategies, but these are typically not shared across languages. More importantly, POSIX declares modifying the environment in a multi-threaded process as unsafe, and `getenv` in libc can't be changed to take a lock because it returns a pointer to the data (see [rust#27970] for more discussion). Since version 4.20 chrono no longer uses `localtime_r`, instead using Rust code to query the timezone (from the `TZ` variable or via `iana-time-zone` as a fallback) and work with data from the system timezone database directly. The code for this was forked from the [tz-rs crate] by [@x-hgg-x](https://togithub.com/x-hgg-x). As such, chrono now respects the Rust lock when reading the `TZ` environment variable. In general, code should avoid modifying the environment. [CVE-2020-26235]: https://nvd.nist.gov/vuln/detail/CVE-2020-26235 [RUSTSEC-2020-0071]: https://rustsec.org/advisories/RUSTSEC-2020-0071 [chrono#499]: https://togithub.com/chronotope/chrono/pull/499 [RUSTSEC-2020-0159]: https://rustsec.org/advisories/RUSTSEC-2020-0159.html [rust#27970]: https://togithub.com/rust-lang/rust/issues/27970 [chrono#677]: https://togithub.com/chronotope/chrono/pull/677 [tz-rs crate]: https://crates.io/crates/tz-rs ##### Removing time 0.1 Because time 0.1 has been unmaintained for years, however, the security advisory mentioned above has not been addressed. While chrono maintainers were careful not to break backwards compatibility with the `time::Duration` type, there has been a long stream of issues from users inquiring about the time 0.1 dependency with the vulnerability. We investigated the potential breakage of removing the time 0.1 dependency in [chrono#1095] using a crater-like experiment and determined that the potential for breaking (public) dependencies is very low. We reached out to those few crates that did still depend on compatibility with time 0.1. As such, for chrono 0.4.30 we have decided to swap out the time 0.1 `Duration` implementation for a local one that will offer a strict superset of the existing API going forward. This will prevent most downstream users from being affected by the security vulnerability in time 0.1 while minimizing the ecosystem impact of semver-incompatible version churn. [chrono#1095]: https://togithub.com/chronotope/chrono/pull/1095 Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.29`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.29) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.28...v0.4.29) This release fixes a panic introduced in chrono 0.4.27 in `FromStr<DateTime<Utc>>` ([#1253](https://togithub.com/chronotope/chrono/issues/1253)). Chrono now has a [Discord channel](https://discord.gg/sXpav4PS7M). #### Fixes - Fix arbitrary string slicing in `parse_rfc3339_relaxed` ([#1254](https://togithub.com/chronotope/chrono/issues/1254)) #### Deprecations - Deprecate `TimeZone::datetime_from_str` ([#1251](https://togithub.com/chronotope/chrono/issues/1251)) #### Documentation - Correct documentation for `FromStr` for `Weekday` and `Month` ([#1226](https://togithub.com/chronotope/chrono/issues/1226), thanks [@wfraser](https://togithub.com/wfraser)) #### Internal improvements - Revert "add test_issue\_866" ([#1238](https://togithub.com/chronotope/chrono/issues/1238)) - CI: run tests on `i686` and `wasm32-wasi` ([#1237](https://togithub.com/chronotope/chrono/issues/1237)) - CI: Include doctests for code coverage ([#1248](https://togithub.com/chronotope/chrono/issues/1248)) - Move benchmarks to a separate crate ([#1243](https://togithub.com/chronotope/chrono/issues/1243)) This allows us to upgrade the criterion dependency to 5.1 without changing our MSRV. - Add Discord link to README ([#1240](https://togithub.com/chronotope/chrono/issues/1240), backported in [#1256](https://togithub.com/chronotope/chrono/issues/1256)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.28`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.28) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.27...v0.4.28) This release fixes a test failure on 32-bit targets introduced with 0.4.27, see [https://github.com/chronotope/chrono/issues/1234](https://togithub.com/chronotope/chrono/issues/1234). ### [`v0.4.27`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.27) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.26...v0.4.27) This release bumps the MSRV from 1.56 to 1.57. This allows us to take advantage of the panicking in const feature. In this release most methods on `NaiveDate` and `NaiveTime` are made const, `NaiveDateTime` and others will follow in a later release. The parser for the `%+` formatting specifier and the `RFC3339` formatting item is switched from a strict to a relaxed parser (see [https://github.com/chronotope/chrono/pull/1145](https://togithub.com/chronotope/chrono/pull/1145)). This matches the existing documentation, and the parser used by `DateTime::from_str`. If you need to validate the input, consider using `DateTime::from_rfc3339`. #### Deprecations - Deprecate `DateTime::{from_local, from_utc}` ([https://github.com/chronotope/chrono/pull/1175](https://togithub.com/chronotope/chrono/pull/1175)) #### Additions - Let `DateTime::signed_duration_since` take argument with `Borrow` ([https://github.com/chronotope/chrono/pull/1119](https://togithub.com/chronotope/chrono/pull/1119)) - Implement `PartialOrd` for `Month` ([https://github.com/chronotope/chrono/pull/999](https://togithub.com/chronotope/chrono/pull/999), thanks [@Munksgaard](https://togithub.com/Munksgaard)) - Add `Ord` and `Eq` for types which already derive `PartialOrd` and `PartialEq` ([https://github.com/chronotope/chrono/pull/1128](https://togithub.com/chronotope/chrono/pull/1128), thanks [@totikom](https://togithub.com/totikom)) - implement `FusedIterator` for `NaiveDateDaysIterator` and `NaiveDateWeeksIterator` ([https://github.com/chronotope/chrono/pull/1134](https://togithub.com/chronotope/chrono/pull/1134)) - Make `NaiveDateDaysIterator` and `NaiveDateWeeksIterator` public ([https://github.com/chronotope/chrono/pull/1134](https://togithub.com/chronotope/chrono/pull/1134)) - Add `FromStr` for `FixedOffset` ([https://github.com/chronotope/chrono/pull/1157](https://togithub.com/chronotope/chrono/pull/1157), thanks [@mcronce](https://togithub.com/mcronce)) - Remove `Tz::Offset: Display` requirement from `DateTime::to_rfc*` ([https://github.com/chronotope/chrono/pull/1160](https://togithub.com/chronotope/chrono/pull/1160)) - More flexible offset formatting (not exposed yet) ([https://github.com/chronotope/chrono/pull/1160](https://togithub.com/chronotope/chrono/pull/1160)) - Make `StrftimeItems` with `unstable-locales` work without allocating ([https://github.com/chronotope/chrono/pull/1152](https://togithub.com/chronotope/chrono/pull/1152)) - Make `NaiveDate::from_ymd_opt` const ([https://github.com/chronotope/chrono/pull/1172](https://togithub.com/chronotope/chrono/pull/1172), thanks [@kamadorueda](https://togithub.com/kamadorueda)) - Implement `Error` trait for `ParseWeekdayError` and `ParseMonthError` ([https://github.com/chronotope/chrono/pull/539](https://togithub.com/chronotope/chrono/pull/539), thanks [@mike-kfed](https://togithub.com/mike-kfed)) - Make methods on `NaiveTime` const, update MSRV to 1.57 ([https://github.com/chronotope/chrono/pull/1080](https://togithub.com/chronotope/chrono/pull/1080)) - Make methods on `NaiveDate` const ([https://github.com/chronotope/chrono/pull/1205](https://togithub.com/chronotope/chrono/pull/1205)) - Implement operations for `core::time::Duration` on `DateTime` types ([https://github.com/chronotope/chrono/pull/1229](https://togithub.com/chronotope/chrono/pull/1229)) #### Fixes - Ensure `timestamp_nanos` panics on overflow in release builds ([https://github.com/chronotope/chrono/pull/1123](https://togithub.com/chronotope/chrono/pull/1123)) - Fix `offset_from_local_datetime` for `wasm_bindgen` ([https://github.com/chronotope/chrono/pull/1131](https://togithub.com/chronotope/chrono/pull/1131)) - Parsing: Consider `%s` to be a timestamp in UTC ([https://github.com/chronotope/chrono/pull/1136](https://togithub.com/chronotope/chrono/pull/1136)) - Don't panic when formatting with `%#z` ([https://github.com/chronotope/chrono/pull/1140](https://togithub.com/chronotope/chrono/pull/1140), thanks [@domodwyer](https://togithub.com/domodwyer)) - Parsing: allow MINUS SIGN (U+2212) in offset ([https://github.com/chronotope/chrono/pull/1087](https://togithub.com/chronotope/chrono/pull/1087), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - Fix locale formatting for `%c` and `%r` ([https://github.com/chronotope/chrono/pull/1165](https://togithub.com/chronotope/chrono/pull/1165)) - Localize decimal point with `unstable-locales` feature ([https://github.com/chronotope/chrono/pull/1168](https://togithub.com/chronotope/chrono/pull/1168)) - Fix panic on macOS 10.12 caused by using version 1 of the TZif file format ([https://github.com/chronotope/chrono/pull/1201](https://togithub.com/chronotope/chrono/pull/1201), thanks to help from [@jfro](https://togithub.com/jfro)) - Fix deserialization of negative timestamps ([https://github.com/chronotope/chrono/pull/1194](https://togithub.com/chronotope/chrono/pull/1194)) - Do not use `Offset`'s `Debug` impl when serializing `DateTime` ([https://github.com/chronotope/chrono/pull/1035](https://togithub.com/chronotope/chrono/pull/1035)) - Allow missing seconds in `NaiveTime::from_str` ([https://github.com/chronotope/chrono/pull/1181](https://togithub.com/chronotope/chrono/pull/1181)) - Do not depend on `android-tzdata` if the `clock` feature is not enabled ([https://github.com/chronotope/chrono/pull/1220](https://togithub.com/chronotope/chrono/pull/1220), thanks [@AlexTMjugador](https://togithub.com/AlexTMjugador)) - Small fixes to the RFC 3339 parsers ([https://github.com/chronotope/chrono/pull/1145](https://togithub.com/chronotope/chrono/pull/1145)) #### Documentation - Add "Errors" and "Panics" sections to API docs ([https://github.com/chronotope/chrono/pull/1120](https://togithub.com/chronotope/chrono/pull/1120)) - Specify licenses in SPDX format ([https://github.com/chronotope/chrono/pull/1132](https://togithub.com/chronotope/chrono/pull/1132), backport of [https://github.com/chronotope/chrono/issues/910](https://togithub.com/chronotope/chrono/issues/910), thanks [@LingMan](https://togithub.com/LingMan)) - Fix `NaiveTime` doc typo ([https://github.com/chronotope/chrono/pull/1146](https://togithub.com/chronotope/chrono/pull/1146), thanks [@zachs18](https://togithub.com/zachs18)) - Clarify nanosecond formatting specifier doc ([https://github.com/chronotope/chrono/pull/1173](https://togithub.com/chronotope/chrono/pull/1173)) - Add warning against combining multiple `Datelike::with_*` ([https://github.com/chronotope/chrono/pull/1199](https://togithub.com/chronotope/chrono/pull/1199)) - Fix typo "accepted" ([https://github.com/chronotope/chrono/pull/1209](https://togithub.com/chronotope/chrono/pull/1209), thanks [@simon04](https://togithub.com/simon04)) - Add some examples to `Utc::now` and `Local::now` ([https://github.com/chronotope/chrono/pull/1192](https://togithub.com/chronotope/chrono/pull/1192)) - Add example to `Weekday::num_days_from_monday` ([https://github.com/chronotope/chrono/pull/1193](https://togithub.com/chronotope/chrono/pull/1193)) - Fix some comments and panic messages ([https://github.com/chronotope/chrono/pull/1221](https://togithub.com/chronotope/chrono/pull/1221), thanks [@umanwizard](https://togithub.com/umanwizard)) #### Internal improvements - `DateTime::to_rfc_*` optimizations ([https://github.com/chronotope/chrono/pull/1200](https://togithub.com/chronotope/chrono/pull/1200)) - Move all tests into modules, fix clippy warnings ([https://github.com/chronotope/chrono/pull/1138](https://togithub.com/chronotope/chrono/pull/1138)) - Offset parsing cleanup ([https://github.com/chronotope/chrono/pull/1158](https://togithub.com/chronotope/chrono/pull/1158)) - Factor out formatting to `format/formatting.rs` ([https://github.com/chronotope/chrono/pull/1156](https://togithub.com/chronotope/chrono/pull/1156)) - Format refactorings ([https://github.com/chronotope/chrono/pull/1198](https://togithub.com/chronotope/chrono/pull/1198)) - Format toml files with taplo ([https://github.com/chronotope/chrono/pull/1117](https://togithub.com/chronotope/chrono/pull/1117), thanks [@tottoto](https://togithub.com/tottoto)) - Stop vendoring `saturating_abs` ([https://github.com/chronotope/chrono/pull/1124](https://togithub.com/chronotope/chrono/pull/1124)) - CI: shell set -eux, use bash ([https://github.com/chronotope/chrono/pull/1103](https://togithub.com/chronotope/chrono/pull/1103), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - Fix dead code error when running dateutils test on Windows ([https://github.com/chronotope/chrono/pull/1125](https://togithub.com/chronotope/chrono/pull/1125)) - Remove `Makefile` ([https://github.com/chronotope/chrono/pull/1133](https://togithub.com/chronotope/chrono/pull/1133)) - CI: Test `wasm-bindgen` feature ([https://github.com/chronotope/chrono/pull/1131](https://togithub.com/chronotope/chrono/pull/1131)) - Stop using deprecated methods in parse module ([https://github.com/chronotope/chrono/pull/1142](https://togithub.com/chronotope/chrono/pull/1142)) - Add formatting benchmarks ([https://github.com/chronotope/chrono/pull/1155](https://togithub.com/chronotope/chrono/pull/1155)) - Feature gate tests instead of methods ([https://github.com/chronotope/chrono/pull/1159](https://togithub.com/chronotope/chrono/pull/1159), [https://github.com/chronotope/chrono/pull/1162](https://togithub.com/chronotope/chrono/pull/1162)) - Parallelize `try_verify_against_date_command` ([https://github.com/chronotope/chrono/pull/1161](https://togithub.com/chronotope/chrono/pull/1161)) - CI: also run integration tests with `no_std` ([https://github.com/chronotope/chrono/pull/1166](https://togithub.com/chronotope/chrono/pull/1166)) - Split ` test_parse ` ([https://github.com/chronotope/chrono/pull/1170](https://togithub.com/chronotope/chrono/pull/1170)) - Remove `#![deny(dead_code)]` ([https://github.com/chronotope/chrono/pull/1187](https://togithub.com/chronotope/chrono/pull/1187)) - Clippy fixes for Rust 1.71 ([https://github.com/chronotope/chrono/pull/1186](https://togithub.com/chronotope/chrono/pull/1186)) - Various small improvements ([https://github.com/chronotope/chrono/pull/1191](https://togithub.com/chronotope/chrono/pull/1191)) - Add unit test for uncovered regions ([https://github.com/chronotope/chrono/pull/1149](https://togithub.com/chronotope/chrono/pull/1149), thanks [@CXWorks](https://togithub.com/CXWorks)) - Don't test the same thing twice in `test_date_extreme_offset` ([https://github.com/chronotope/chrono/pull/1195](https://togithub.com/chronotope/chrono/pull/1195)) - CI: Add workflow code coverage report and upload ([https://github.com/chronotope/chrono/pull/1178](https://togithub.com/chronotope/chrono/pull/1178), [https://github.com/chronotope/chrono/pull/1215](https://togithub.com/chronotope/chrono/pull/1215), thanks [@jtmoon79](https://togithub.com/jtmoon79)) - CI: fail on warnings in `features-check` ([https://github.com/chronotope/chrono/pull/1216](https://togithub.com/chronotope/chrono/pull/1216)) - Switch to windows-bindgen ([https://github.com/chronotope/chrono/pull/1202](https://togithub.com/chronotope/chrono/pull/1202), thanks to help from [@MarijnS95](https://togithub.com/MarijnS95)) Thanks to all contributors on behalf of the chrono team, [@djc](https://togithub.com/djc) and [@pitdicker](https://togithub.com/pitdicker)! ### [`v0.4.26`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.26) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.25...v0.4.26) The changes from [#807](https://togithub.com/chronotope/chrono/issues/807) we merged for 0.4.25 unfortunately restricted parsing in a way that was incompatible with earlier 0.4.x releases. We reverted this in [#1113](https://togithub.com/chronotope/chrono/issues/1113). A small amount of other changes were merged since. - Update README ([#1111](https://togithub.com/chronotope/chrono/issues/1111), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Revert backport of [#807](https://togithub.com/chronotope/chrono/issues/807) ([#1113](https://togithub.com/chronotope/chrono/issues/1113), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Update to 2021 edition ([#1109](https://togithub.com/chronotope/chrono/issues/1109), thanks to [@tottoto](https://togithub.com/tottoto)) - Fix `DurationRound` panics from issue [#1010](https://togithub.com/chronotope/chrono/issues/1010) ([#1093](https://togithub.com/chronotope/chrono/issues/1093), thanks to [@pitdicker](https://togithub.com/pitdicker)) - tests: date path consolidate (branch 0.4.x) ([#1090](https://togithub.com/chronotope/chrono/issues/1090), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - Parse tests nanosecond bare dot (branch 0.4.x) ([#1098](https://togithub.com/chronotope/chrono/issues/1098), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - yamllint cleanup lint.yml test.yml ([#1102](https://togithub.com/chronotope/chrono/issues/1102), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - Remove num-iter dependency ([#1107](https://togithub.com/chronotope/chrono/issues/1107), thanks to [@tottoto](https://togithub.com/tottoto)) Thanks on behalf of the chrono team ([@djc](https://togithub.com/djc) and [@esheppa](https://togithub.com/esheppa)) to all contributors! ### [`v0.4.25`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.25) [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.24...v0.4.25) Time for another maintenance release. This release bumps the MSRV to 1.56; given MSRV bumps in chrono's dependencies (notably for syn 2), we felt that it no longer made sense to support any older versions. Feedback welcome in our issue tracker! #### Additions - Bump the MSRV to 1.56 ([#1053](https://togithub.com/chronotope/chrono/issues/1053)) - Apply comments from MSRV bump ([#1026](https://togithub.com/chronotope/chrono/issues/1026), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Remove num-integer dependency ([#1037](https://togithub.com/chronotope/chrono/issues/1037), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `NaiveDateTime::and_utc()` method ([#952](https://togithub.com/chronotope/chrono/issues/952), thanks to [@klnusbaum](https://togithub.com/klnusbaum)) - derive `Hash` for most pub types that also derive `PartialEq` ([#938](https://togithub.com/chronotope/chrono/issues/938), thanks to [@bruceg](https://togithub.com/bruceg)) - Add `parse_and_remainder()` methods ([#1011](https://togithub.com/chronotope/chrono/issues/1011), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `DateTime::fix_offset()` ([#1030](https://togithub.com/chronotope/chrono/issues/1030), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `#[track_caller]` to `LocalResult::unwrap` ([#1046](https://togithub.com/chronotope/chrono/issues/1046), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add `#[must_use]` to some methods ([#1007](https://togithub.com/chronotope/chrono/issues/1007), thanks to [@aceArt-GmbH](https://togithub.com/aceArt-GmbH)) - Implement `PartialOrd` for `Month` ([#999](https://togithub.com/chronotope/chrono/issues/999), thanks to [@Munksgaard](https://togithub.com/Munksgaard)) - Add `impl From<NaiveDateTime> for NaiveDate` ([#1012](https://togithub.com/chronotope/chrono/issues/1012), thanks to [@pezcore](https://togithub.com/pezcore)) - Extract timezone info from tzdata file on Android ([#978](https://togithub.com/chronotope/chrono/issues/978), thanks to [@RumovZ](https://togithub.com/RumovZ)) #### Fixes - Prevent string slicing inside char boundaries ([#1024](https://togithub.com/chronotope/chrono/issues/1024), thanks to [@pitdicker](https://togithub.com/pitdicker)) - fix IsoWeek so that its flags are always correct ([#991](https://togithub.com/chronotope/chrono/issues/991), thanks to [@moshevds](https://togithub.com/moshevds)) - Fix out-of-range panic in `NaiveWeek::last_day` ([#1070](https://togithub.com/chronotope/chrono/issues/1070), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Use correct offset in conversion from `Local` to `FixedOffset` ([#1041](https://togithub.com/chronotope/chrono/issues/1041), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix military timezones in RFC 2822 parsing ([#1013](https://togithub.com/chronotope/chrono/issues/1013), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Guard against overflow in NaiveDate::with_\*0 methods ([#1023](https://togithub.com/chronotope/chrono/issues/1023), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix panic in from_num_days_from_ce_opt ([#1052](https://togithub.com/chronotope/chrono/issues/1052), thanks to [@pitdicker](https://togithub.com/pitdicker)) #### Refactoring - Rely on std for getting local time offset ([#1072](https://togithub.com/chronotope/chrono/issues/1072), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Make functions in internals const ([#1043](https://togithub.com/chronotope/chrono/issues/1043), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Refactor windows module in `Local` ([#992](https://togithub.com/chronotope/chrono/issues/992), thanks to [@nekevss](https://togithub.com/nekevss)) - Simplify from_timestamp_millis, from_timestamp_micros ([#1032](https://togithub.com/chronotope/chrono/issues/1032), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Backport [#983](https://togithub.com/chronotope/chrono/issues/983) and [#1000](https://togithub.com/chronotope/chrono/issues/1000) ([#1063](https://togithub.com/chronotope/chrono/issues/1063), thanks to [@pitdicker](https://togithub.com/pitdicker)) #### Documentation - Backport documentation improvements ([#1066](https://togithub.com/chronotope/chrono/issues/1066), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add documentation for %Z quirk ([#1051](https://togithub.com/chronotope/chrono/issues/1051), thanks to [@campbellcole](https://togithub.com/campbellcole)) - Add an example to Weekday ([#1019](https://togithub.com/chronotope/chrono/issues/1019), thanks to [@pitdicker](https://togithub.com/pitdicker)) #### Internal improvements - Gate test on `clock` feature ([#1061](https://togithub.com/chronotope/chrono/issues/1061), thanks to [@pitdicker](https://togithub.com/pitdicker)) - CI: Also run tests with `--no-default-features` ([#1059](https://togithub.com/chronotope/chrono/issues/1059), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Prevent `bench_year_flags_from_year` from being optimized out ([#1034](https://togithub.com/chronotope/chrono/issues/1034), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix test_leap_second during DST transition ([#1064](https://togithub.com/chronotope/chrono/issues/1064), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix warnings when running tests on Windows ([#1038](https://togithub.com/chronotope/chrono/issues/1038), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Fix tests on AIX ([#1028](https://togithub.com/chronotope/chrono/issues/1028), thanks to [@ecnelises](https://togithub.com/ecnelises)) - Fix doctest warnings, remove mention of deprecated methods from main doc ([#1081](https://togithub.com/chronotope/chrono/issues/1081), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Reformat `test_datetime_parse_from_str` ([#1078](https://togithub.com/chronotope/chrono/issues/1078), thanks to [@pitdicker](https://togithub.com/pitdicker)) - GitHub yml shell `set -eux`, use bash ([#1103](https://togithub.com/chronotope/chrono/issues/1103), thanks to [@jtmoon79](https://togithub.com/jtmoon79)) - test: explicitly set `LANG` to `c` in gnu `date` ([#1089](https://togithub.com/chronotope/chrono/issues/1089), thanks to [@scarf005](https://togithub.com/scarf005)) - Switch test to `TryFrom` ([#1086](https://togithub.com/chronotope/chrono/issues/1086), thanks to [@pitdicker](https://togithub.com/pitdicker)) - Add test for issue 551 ([#1020](https://togithub.com/chronotope/chrono/issues/1020), thanks to [@pitdicker](https://togithub.com/pitdicker)) - RFC 2822 single-letter obsolete tests ([#1014](https://togithub.com/chronotope/chrono/issues/1014), thanks to [@jtmoon79](h </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/X-oss-byte/Nextjs).

Add history of chrono and time 0.1 to main documentation

a83ff4a

djc approved these changes Sep 7, 2023

View reviewed changes

pitdicker merged commit 7387fe7 into chronotope:0.4.x Sep 7, 2023
37 checks passed

pitdicker deleted the chrono_and_time_0.1 branch September 7, 2023 10:28

pitdicker mentioned this pull request Jan 31, 2024

Remove stray documentation #1397

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add history of chrono and time 0.1 to main documentation #1264

Add history of chrono and time 0.1 to main documentation #1264

pitdicker commented Sep 7, 2023

djc commented Sep 7, 2023

pitdicker commented Sep 7, 2023

codecov bot commented Sep 7, 2023

Add history of chrono and time 0.1 to main documentation #1264

Add history of chrono and time 0.1 to main documentation #1264

Conversation

pitdicker commented Sep 7, 2023

djc commented Sep 7, 2023

pitdicker commented Sep 7, 2023

codecov bot commented Sep 7, 2023

Codecov Report