search

trinsic-id / v2-sdk

Trinsic SDK repository
https://docs.trinsic.id/
Apache License 2.0
29 stars 15 forks source link

chore(deps): update all cargo dependencies #1628

Open fundthmcalculus opened 6 months ago

fundthmcalculus commented 6 months ago

This PR contains the following updates:

Package Type Update Change
base64 dependencies minor 0.13.1 -> 0.22.0
blake3 dependencies minor 1.3.3 -> 1.5.1
bytes dependencies minor 1.4.0 -> 1.6.0
chrono dependencies patch 0.4.24 -> 0.4.38
clap dependencies patch 3.2.23 -> 3.2.25
colored dependencies minor 2.0.0 -> 2.1.0
prost dependencies minor 0.11 -> 0.12
prost-types dependencies minor 0.11 -> 0.12
serde (source) dependencies patch 1.0.160 -> 1.0.203
serde_json dependencies patch 1.0.96 -> 1.0.117
tokio (source) dependencies minor 1.27.0 -> 1.38.0
toml dependencies minor 0.5.11 -> 0.8.0
tonic dependencies minor 0.8 -> 0.11
tonic-build build-dependencies minor 0.8 -> 0.11

Release Notes

marshallpierce/rust-base64 (base64) ### [`v0.22.1`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0221) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.22.0...v0.22.1) - Correct the symbols used for the predefined `alphabet::BIN_HEX`. ### [`v0.22.0`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0220) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.21.7...v0.22.0) - `DecodeSliceError::OutputSliceTooSmall` is now conservative rather than precise. That is, the error will only occur if the decoded output *cannot* fit, meaning that `Engine::decode_slice` can now be used with exactly-sized output slices. As part of this, `Engine::internal_decode` now returns `DecodeSliceError` instead of `DecodeError`, but that is not expected to affect any external callers. - `DecodeError::InvalidLength` now refers specifically to the *number of valid symbols* being invalid (i.e. `len % 4 == 1`), rather than just the number of input bytes. This avoids confusing scenarios when based on interpretation you could make a case for either `InvalidLength` or `InvalidByte` being appropriate. - Decoding is somewhat faster (5-10%) ### [`v0.21.7`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0217) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.21.6...v0.21.7) - Support getting an alphabet's contents as a str via `Alphabet::as_str()` ### [`v0.21.6`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0216) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.21.5...v0.21.6) - Improved introductory documentation and example ### [`v0.21.5`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0215) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.21.4...v0.21.5) - Add `Debug` and `Clone` impls for the general purpose Engine ### [`v0.21.4`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0214) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.21.3...v0.21.4) - Make `encoded_len` `const`, allowing the creation of arrays sized to encode compile-time-known data lengths ### [`v0.21.3`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0213) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.21.2...v0.21.3) - Implement `source` instead of `cause` on Error types - Roll back MSRV to 1.48.0 so Debian can continue to live in a time warp - Slightly faster chunked encoding for short inputs - Decrease binary size ### [`v0.21.2`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0212) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.21.1...v0.21.2) - Rollback MSRV to 1.57.0 -- only dev dependencies need 1.60, not the main code ### [`v0.21.1`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0211) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.21.0...v0.21.1) - Remove the possibility of panicking during decoded length calculations - `DecoderReader` no longer sometimes erroneously ignores padding [#​226](https://togithub.com/marshallpierce/rust-base64/issues/226) #### Breaking changes - `Engine.internal_decode` return type changed - Update MSRV to 1.60.0 ### [`v0.21.0`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0210) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.20.0...v0.21.0) #### Migration ##### Functions | < 0.20 function | 0.21 equivalent | |-------------------------|-------------------------------------------------------------------------------------| | `encode()` | `engine::general_purpose::STANDARD.encode()` or `prelude::BASE64_STANDARD.encode()` | | `encode_config()` | `engine.encode()` | | `encode_config_buf()` | `engine.encode_string()` | | `encode_config_slice()` | `engine.encode_slice()` | | `decode()` | `engine::general_purpose::STANDARD.decode()` or `prelude::BASE64_STANDARD.decode()` | | `decode_config()` | `engine.decode()` | | `decode_config_buf()` | `engine.decode_vec()` | | `decode_config_slice()` | `engine.decode_slice()` | The short-lived 0.20 functions were the 0.13 functions with `config` replaced with `engine`. ##### Padding If applicable, use the preset engines `engine::STANDARD`, `engine::STANDARD_NO_PAD`, `engine::URL_SAFE`, or `engine::URL_SAFE_NO_PAD`. The `NO_PAD` ones require that padding is absent when decoding, and the others require that canonical padding is present . If you need the < 0.20 behavior that did not care about padding, or want to recreate < 0.20.0's predefined `Config`s precisely, see the following table. | 0.13.1 Config | 0.20.0+ alphabet | `encode_padding` | `decode_padding_mode` | |-----------------|------------------|------------------|-----------------------| | STANDARD | STANDARD | true | Indifferent | | STANDARD_NO_PAD | STANDARD | false | Indifferent | | URL_SAFE | URL_SAFE | true | Indifferent | | URL_SAFE_NO_PAD | URL_SAFE | false | Indifferent | ### [`v0.20.0`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0200) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.13.1...v0.20.0) #### Breaking changes - Update MSRV to 1.57.0 - Decoding can now either ignore padding, require correct padding, or require no padding. The default is to require correct padding. - The `NO_PAD` config now requires that padding be absent when decoding. #### 0.20.0-alpha.1 ##### Breaking changes - Extended the `Config` concept into the `Engine` abstraction, allowing the user to pick different encoding / decoding implementations. - What was formerly the only algorithm is now the `FastPortable` engine, so named because it's portable (works on any CPU) and relatively fast. - This opens the door to a portable constant-time implementation ([#​153](https://togithub.com/marshallpierce/rust-base64/pull/153), presumably `ConstantTimePortable`?) for security-sensitive applications that need side-channel resistance, and CPU-specific SIMD implementations for more speed. - Standard base64 per the RFC is available via `DEFAULT_ENGINE`. To use different alphabets or other settings ( padding, etc), create your own engine instance. - `CharacterSet` is now `Alphabet` (per the RFC), and allows creating custom alphabets. The corresponding tables that were previously code-generated are now built dynamically. - Since there are already multiple breaking changes, various functions are renamed to be more consistent and discoverable. - MSRV is now 1.47.0 to allow various things to use `const fn`. - `DecoderReader` now owns its inner reader, and can expose it via `into_inner()`. For symmetry, `EncoderWriter` can do the same with its writer. - `encoded_len` is now public so you can size encode buffers precisely.
BLAKE3-team/BLAKE3 (blake3) ### [`v1.5.1`](https://togithub.com/BLAKE3-team/BLAKE3/releases/tag/1.5.1) [Compare Source](https://togithub.com/BLAKE3-team/BLAKE3/compare/1.5.0...1.5.1) version 1.5.1 Changes since 1.5.0: - The Rust crate is now compatible with Miri. - \~1% performance improvement on Arm NEON contributed by [@​divinity76](https://togithub.com/divinity76) ([#​384](https://togithub.com/BLAKE3-team/BLAKE3/issues/384)). - Various fixes and improvements in the CMake build. - The MSRV of b3sum is now 1.74.1. (The MSRV of the library crate is unchanged, 1.66.1.) ### [`v1.5.0`](https://togithub.com/BLAKE3-team/BLAKE3/releases/tag/1.5.0) [Compare Source](https://togithub.com/BLAKE3-team/BLAKE3/compare/1.4.1...1.5.0) version 1.5.0 Changes since 1.4.1: - The Rust crate's Hasher type has gained new helper methods for common forms of IO: update_reader, update_mmap, and update_mmap_rayon. The latter matches the default behavior of b3sum. The mmap methods are gated by the new "mmap" Cargo feature. - Most of the Rust crate's public types now implement the Zeroize trait. This is gated by the new "zeroize" Cargo feature. - The Rust crate's Hash types now implements the serde Serialize and Deserialize traits. This is gated by the new "serde" Cargo feature. - The C library now uses atomics to cache detected CPU features under most compilers other than MSVC. Previously this was a non-atomic write, which was probably "benign" but made TSan unhappy. - NEON support is now disabled by default on big-endian AArch64. Previously this was a build error if the caller didn't explicitly disable it. ### [`v1.4.1`](https://togithub.com/BLAKE3-team/BLAKE3/releases/tag/1.4.1) [Compare Source](https://togithub.com/BLAKE3-team/BLAKE3/compare/1.4.0...1.4.1) version 1.4.1 Changes since 1.4.0: - Improved performance in the ARM NEON implementation for both C and Rust callers. This affects AArch64 targets by default and ARMv7 targets that explicitly enable (and support) NEON. The size of the improvement depends on the microarchitecture, but I've benchmarked \~1.3x on a Cortex-A53 and ~1.2x on an Apple M1. Contributed by [@​sdlyyxy](https://togithub.com/sdlyyxy) in [#​319](https://togithub.com/BLAKE3-team/BLAKE3/issues/319). - The MSRV is now 1.66.1 for both the `blake3` crate and `b3sum`. ### [`v1.4.0`](https://togithub.com/BLAKE3-team/BLAKE3/releases/tag/1.4.0) [Compare Source](https://togithub.com/BLAKE3-team/BLAKE3/compare/1.3.3...1.4.0) version 1.4.0 Changes since 1.3.3: - The C implementation provides a `CMakeLists.txt` for callers who build with CMake. The CMake build is not yet stable, and callers should expect breaking changes in patch version updates. The "by hand" build will always continue to be supported and documented. - `b3sum` supports the `--seek` flag, to set the starting position in the output stream. - `b3sum --check` prints a summary of errors to stderr. - `Hash::as_bytes` is const. - `Hash` supports `from_bytes`, which is const.
tokio-rs/bytes (bytes) ### [`v1.6.0`](https://togithub.com/tokio-rs/bytes/blob/HEAD/CHANGELOG.md#160-March-22-2024) [Compare Source](https://togithub.com/tokio-rs/bytes/compare/v1.5.0...v1.6.0) ##### Added - Add `Bytes::is_unique` ([#​643](https://togithub.com/tokio-rs/bytes/issues/643)) ##### Documented - Fix changelog typo ([#​628](https://togithub.com/tokio-rs/bytes/issues/628)) - Fix some spelling mistakes ([#​633](https://togithub.com/tokio-rs/bytes/issues/633)) - Typo fix ([#​637](https://togithub.com/tokio-rs/bytes/issues/637)) - Fix broken links ([#​639](https://togithub.com/tokio-rs/bytes/issues/639)) - Add security policy ([#​649](https://togithub.com/tokio-rs/bytes/issues/649)) ##### Internal changes - Move comment to correct constant ([#​629](https://togithub.com/tokio-rs/bytes/issues/629)) - Various cleanup ([#​635](https://togithub.com/tokio-rs/bytes/issues/635)) - Simplify `UninitSlice::as_uninit_slice_mut()` logic ([#​644](https://togithub.com/tokio-rs/bytes/issues/644)) - Use `self.` instead of `Self::` ([#​642](https://togithub.com/tokio-rs/bytes/issues/642)) - `BytesMut`: Assert alignment of `Shared` ([#​652](https://togithub.com/tokio-rs/bytes/issues/652)) - Remove unnecessary namespace qualifier ([#​660](https://togithub.com/tokio-rs/bytes/issues/660)) - Remove an unnecessary else branch ([#​662](https://togithub.com/tokio-rs/bytes/issues/662)) - Remove unreachable else branch ([#​661](https://togithub.com/tokio-rs/bytes/issues/661)) - make parameter mut in `From` ([#​667](https://togithub.com/tokio-rs/bytes/issues/667)) - Restore commented tests ([#​665](https://togithub.com/tokio-rs/bytes/issues/665)) - Use `sub` instead of `offset` ([#​668](https://togithub.com/tokio-rs/bytes/issues/668)) - Calculate original capacity only if necessary ([#​666](https://togithub.com/tokio-rs/bytes/issues/666)) - `set_vec_pos` does not need a second parameter ([#​672](https://togithub.com/tokio-rs/bytes/issues/672)) - `get_vec_pos`: use `&self` instead of `&mut self` ([#​670](https://togithub.com/tokio-rs/bytes/issues/670)) - Refactor `split_at`/`split_to` ([#​663](https://togithub.com/tokio-rs/bytes/issues/663)) - Use `Iterator` from the prelude ([#​673](https://togithub.com/tokio-rs/bytes/issues/673)) - `copy_to_bytes`: Add panic section to docs ([#​676](https://togithub.com/tokio-rs/bytes/issues/676)) - Remove redundant reserve call ([#​674](https://togithub.com/tokio-rs/bytes/issues/674)) - Use `ManuallyDrop` instead of `mem::forget` ([#​675](https://togithub.com/tokio-rs/bytes/issues/675)) ### [`v1.5.0`](https://togithub.com/tokio-rs/bytes/blob/HEAD/CHANGELOG.md#150-September-7-2023) [Compare Source](https://togithub.com/tokio-rs/bytes/compare/v1.4.0...v1.5.0) ##### Added - Add `UninitSlice::{new,uninit}` ([#​598](https://togithub.com/tokio-rs/bytes/issues/598), [#​599](https://togithub.com/tokio-rs/bytes/issues/599)) - Implement `BufMut` for `&mut [MaybeUninit]` ([#​597](https://togithub.com/tokio-rs/bytes/issues/597)) ##### Changed - Mark `BytesMut::extend_from_slice` as inline ([#​595](https://togithub.com/tokio-rs/bytes/issues/595))
chronotope/chrono (chrono) ### [`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` type, or from the `TimeZone` trait. Converting from `NaiveDateTime` to `DateTime` 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`, `Option` and `Option>` 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` 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::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::::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::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>` ([#​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/chrono

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

This PR has been generated by Renovate Bot.