Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(deps): update all non-major dependencies (#79)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [anyhow](https://redirect.github.com/dtolnay/anyhow) | dependencies |
patch | `1.0.71` -> `1.0.93` |
| [backtrace](https://redirect.github.com/rust-lang/backtrace-rs) |
dependencies | patch | `0.3.73` -> `0.3.74` |
| [chrono](https://redirect.github.com/chronotope/chrono) | dependencies
| patch | `0.4.26` -> `0.4.38` |
| [config](https://redirect.github.com/rust-cli/config-rs) |
dependencies | patch | `0.14.0` -> `0.14.1` |
|
[lazy_static](https://redirect.github.com/rust-lang-nursery/lazy-static.rs)
| dependencies | minor | `1.4.0` -> `1.5.0` |
| [prometheus](https://redirect.github.com/tikv/rust-prometheus) |
dependencies | patch | `0.13.3` -> `0.13.4` |
| [reqwest](https://redirect.github.com/seanmonstar/reqwest) |
dependencies | patch | `0.12.4` -> `0.12.9` |
| [rss](https://redirect.github.com/rust-syndication/rss) | dependencies
| patch | `2.0.4` -> `2.0.9` |
| [serde](https://serde.rs)
([source](https://redirect.github.com/serde-rs/serde)) | dependencies |
patch | `1.0.193` -> `1.0.214` |
| [serde_json](https://redirect.github.com/serde-rs/json) | dependencies
| patch | `1.0.109` -> `1.0.132` |
| [temp-env](https://redirect.github.com/vmx/temp-env) |
dev-dependencies | patch | `0.3.4` -> `0.3.6` |
| [tempfile](https://stebalien.com/projects/tempfile-rs/)
([source](https://redirect.github.com/Stebalien/tempfile)) |
dev-dependencies | minor | `3.6.0` -> `3.14.0` |
| [thiserror](https://redirect.github.com/dtolnay/thiserror) |
dependencies | patch | `2.0.1` -> `2.0.2` |
| [tokio](https://tokio.rs)
([source](https://redirect.github.com/tokio-rs/tokio)) | dependencies |
minor | `1.25.0` -> `1.41.1` |
| [tokio-stream](https://tokio.rs)
([source](https://redirect.github.com/tokio-rs/tokio)) | dependencies |
patch | `0.1.14` -> `0.1.16` |
| [tracing](https://tokio.rs)
([source](https://redirect.github.com/tokio-rs/tracing)) | dependencies
| patch | `0.1.37` -> `0.1.40` |
| [tracing-subscriber](https://tokio.rs)
([source](https://redirect.github.com/tokio-rs/tracing)) | dependencies
| patch | `0.3.17` -> `0.3.18` |
---
### Release Notes
<details>
<summary>dtolnay/anyhow (anyhow)</summary>
###
[`v1.0.93`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.93)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.92...1.0.93)
- Update dev-dependencies to `thiserror` v2
###
[`v1.0.92`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.92)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.91...1.0.92)
- Support Rust 1.82's `&raw const` and `&raw mut` syntax inside
`ensure!`
([#​390](https://redirect.github.com/dtolnay/anyhow/issues/390))
###
[`v1.0.91`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.91)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.90...1.0.91)
- Ensure OUT_DIR is left with deterministic contents after build script
execution
([#​388](https://redirect.github.com/dtolnay/anyhow/issues/388))
###
[`v1.0.90`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.90)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.89...1.0.90)
- Documentation improvements
###
[`v1.0.89`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.89)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.88...1.0.89)
- Make anyhow::Error's `UnwindSafe` and `RefUnwindSafe` impl
consistently available between versions of Rust newer and older than
1.72
([#​386](https://redirect.github.com/dtolnay/anyhow/issues/386))
###
[`v1.0.88`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.88)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.87...1.0.88)
- Documentation improvements
###
[`v1.0.87`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.87)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.86...1.0.87)
- Support more APIs, including `Error::new` and `Error::chain`, in
no-std mode on Rust 1.81+
([#​383](https://redirect.github.com/dtolnay/anyhow/issues/383))
###
[`v1.0.86`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.86)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.85...1.0.86)
- Fix parse error in `ensure!` with non-literal after minus sign
([#​373](https://redirect.github.com/dtolnay/anyhow/issues/373))
###
[`v1.0.85`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.85)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.84...1.0.85)
- Improve `ensure!` macro's rules to unblock some rustc pretty-printer
improvements
([#​368](https://redirect.github.com/dtolnay/anyhow/issues/368),
[#​371](https://redirect.github.com/dtolnay/anyhow/issues/371))
###
[`v1.0.84`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.84)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.83...1.0.84)
- Disallow calling `ensure!` through a `Not` impl for a type that is not
`bool`
([#​367](https://redirect.github.com/dtolnay/anyhow/issues/367))
###
[`v1.0.83`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.83)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.82...1.0.83)
- Integrate compile-time checking of cfgs
([#​363](https://redirect.github.com/dtolnay/anyhow/issues/363))
###
[`v1.0.82`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.82)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.81...1.0.82)
- Documentation improvements
###
[`v1.0.81`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.81)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.80...1.0.81)
- Make backtrace support available when using -Dwarnings
([#​354](https://redirect.github.com/dtolnay/anyhow/issues/354))
###
[`v1.0.80`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.80)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.79...1.0.80)
- Fix unused_imports warnings when compiled by rustc 1.78
###
[`v1.0.79`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.79)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.78...1.0.79)
- Work around improperly cached build script result by sccache
([#​340](https://redirect.github.com/dtolnay/anyhow/issues/340))
###
[`v1.0.78`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.78)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.77...1.0.78)
- Reduce spurious rebuilds under RustRover IDE when using a nightly
toolchain
([#​337](https://redirect.github.com/dtolnay/anyhow/issues/337))
###
[`v1.0.77`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.77)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.76...1.0.77)
- Make `anyhow::Error::backtrace` available on stable Rust compilers
1.65+
([#​293](https://redirect.github.com/dtolnay/anyhow/issues/293),
thanks
[@​LukasKalbertodt](https://redirect.github.com/LukasKalbertodt))
###
[`v1.0.76`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.76)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.75...1.0.76)
- Opt in to `unsafe_op_in_unsafe_fn` lint
([#​329](https://redirect.github.com/dtolnay/anyhow/issues/329))
###
[`v1.0.75`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.75)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.74...1.0.75)
- Partially work around rust-analyzer bug
([https://github.com/rust-lang/rust-analyzer/issues/9911](https://redirect.github.com/rust-lang/rust-analyzer/issues/9911))
###
[`v1.0.74`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.74)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.73...1.0.74)
- Add bootstrap workaround to allow rustc to depend on anyhow
([#​320](https://redirect.github.com/dtolnay/anyhow/issues/320),
thanks [@​RalfJung](https://redirect.github.com/RalfJung))
###
[`v1.0.73`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.73)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.72...1.0.73)
- Update backtrace support to nightly's new Error::provide API
([https://github.com/rust-lang/rust/pull/113464](https://redirect.github.com/rust-lang/rust/pull/113464),
[#​319](https://redirect.github.com/dtolnay/anyhow/issues/319))
###
[`v1.0.72`](https://redirect.github.com/dtolnay/anyhow/releases/tag/1.0.72)
[Compare
Source](https://redirect.github.com/dtolnay/anyhow/compare/1.0.71...1.0.72)
- Documentation improvements
</details>
<details>
<summary>rust-lang/backtrace-rs (backtrace)</summary>
###
[`v0.3.74`](https://redirect.github.com/rust-lang/backtrace-rs/releases/tag/0.3.74)
[Compare
Source](https://redirect.github.com/rust-lang/backtrace-rs/compare/0.3.73...0.3.74)
#### What's Changed
- QNX Neutrino 7.0 support, thanks to
[@​nyurik](https://redirect.github.com/nyurik) in
[https://github.com/rust-lang/backtrace-rs/pull/648](https://redirect.github.com/rust-lang/backtrace-rs/pull/648)
- Cleaned up our Android support. This should massively improve
backtraces for ones with the API level sufficient to ship with
libunwind, etc. Unfortunately, it comes at the cost of dropping support
for older ones! Thanks to
[@​fengys](https://redirect.github.com/fengys) in
[https://github.com/rust-lang/backtrace-rs/pull/656](https://redirect.github.com/rust-lang/backtrace-rs/pull/656)
- Made PrintFmt, which was using the `Enum::__NonExhaustiveVariant`
pattern, use `#[non_exhaustive]` for real. Don't @​ me if you were
matching on that! Thanks to
[@​nyurik](https://redirect.github.com/nyurik) in
[https://github.com/rust-lang/backtrace-rs/pull/651](https://redirect.github.com/rust-lang/backtrace-rs/pull/651)
- Massively cleaned up the windows code! We moved from winapi to
windows-sys with windows-targets thanks to
[@​CraftSpider](https://redirect.github.com/CraftSpider) and
[@​ChrisDenton](https://redirect.github.com/ChrisDenton) in
- Don't cast HANDLE to usize and back by
[@​CraftSpider](https://redirect.github.com/CraftSpider) in
[https://github.com/rust-lang/backtrace-rs/pull/635](https://redirect.github.com/rust-lang/backtrace-rs/pull/635)
- Switch from `winapi` to `windows-sys` by
[@​CraftSpider](https://redirect.github.com/CraftSpider) in
[https://github.com/rust-lang/backtrace-rs/pull/641](https://redirect.github.com/rust-lang/backtrace-rs/pull/641)
- Update windows bindings and use windows-targets by
[@​ChrisDenton](https://redirect.github.com/ChrisDenton) in
[https://github.com/rust-lang/backtrace-rs/pull/653](https://redirect.github.com/rust-lang/backtrace-rs/pull/653)
- A bunch of updated dependencies. Thanks
[@​djc](https://redirect.github.com/djc) and
[@​khuey](https://redirect.github.com/khuey)!
- Sorry if you were testing this code in miri! It started yelling about
sussy casts. A lot. We did a bunch of internal cleanups that should make
it quiet down, thanks to
[@​workingjubilee](https://redirect.github.com/workingjubilee) in
[https://github.com/rust-lang/backtrace-rs/pull/641](https://redirect.github.com/rust-lang/backtrace-rs/pull/641)
- Uhhh we had to tweak `dl_iterate_phdr` in
[https://github.com/rust-lang/backtrace-rs/pull/660](https://redirect.github.com/rust-lang/backtrace-rs/pull/660)
after Android revealed it was... kind of unsound actually and not doing
things like checking for null pointers before making slices! WHOOPS!
Thanks to [@​saethlin](https://redirect.github.com/saethlin) for
implementing detection for precisely that in rustc! It's really hard to
find soundness issues in inherited codebases like this one...
#### New Contributors
- [@​CraftSpider](https://redirect.github.com/CraftSpider) made
their first contribution in
[https://github.com/rust-lang/backtrace-rs/pull/635](https://redirect.github.com/rust-lang/backtrace-rs/pull/635)
- [@​fengys1996](https://redirect.github.com/fengys1996) made
their first contribution in
[https://github.com/rust-lang/backtrace-rs/pull/656](https://redirect.github.com/rust-lang/backtrace-rs/pull/656)
- [@​djc](https://redirect.github.com/djc) made their first
contribution in
[https://github.com/rust-lang/backtrace-rs/pull/657](https://redirect.github.com/rust-lang/backtrace-rs/pull/657)
**Full Changelog**:
https://github.com/rust-lang/backtrace-rs/compare/0.3.73...0.3.74
</details>
<details>
<summary>chronotope/chrono (chrono)</summary>
###
[`v0.4.38`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.38)
[Compare
Source](https://redirect.github.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://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1548),
thanks
[@​workingjubilee](https://redirect.github.com/workingjubilee))
##### Additions
- Add `Weekday::days_since`
([#​1249](https://redirect.github.com/chronotope/chrono/issues/1249),
based on
[#​216](https://redirect.github.com/chronotope/chrono/issues/216)
by [@​clarfonthey](https://redirect.github.com/clarfonthey))
- Add `TimeDelta::checked_mul` and `TimeDelta::checked_div`
([#​1565](https://redirect.github.com/chronotope/chrono/issues/1565),
thanks [@​Zomtir](https://redirect.github.com/Zomtir))
##### Fixes
- Return error when rounding with a zero duration
([#​1474](https://redirect.github.com/chronotope/chrono/issues/1474),
thanks [@​Dav1dde](https://redirect.github.com/Dav1dde))
- Manually implement `Copy` for `DateTime` if offset is `Copy`
([#​1573](https://redirect.github.com/chronotope/chrono/issues/1573))
##### Internal
- Inline `test_encodable_json` and `test_decodable_json` functions
([#​1550](https://redirect.github.com/chronotope/chrono/issues/1550))
- CI: Reduce combinations in `cargo hack check`
([#​1553](https://redirect.github.com/chronotope/chrono/issues/1553))
- Refactor formatting code
([#​1335](https://redirect.github.com/chronotope/chrono/issues/1335))
- Optimize number formatting
([#​1558](https://redirect.github.com/chronotope/chrono/issues/1558))
- Only package files needed for building and testing
([#​1554](https://redirect.github.com/chronotope/chrono/issues/1554))
Thanks to all contributors on behalf of the chrono team,
[@​djc](https://redirect.github.com/djc) and
[@​pitdicker](https://redirect.github.com/pitdicker)!
###
[`v0.4.37`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.37)
[Compare
Source](https://redirect.github.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://redirect.github.com/chronotope/chrono/releases/tag/v0.4.36)
from yesterday for the yanked release.
###
[`v0.4.36`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.36)
[Compare
Source](https://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1510))
##### Deprecations
- Revert `TimeDelta` deprecations
([#​1543](https://redirect.github.com/chronotope/chrono/issues/1543))
- Deprecate `TimeStamp::timestamp_subsec_nanos`, which was missed in the
0.4.35 release
([#​1486](https://redirect.github.com/chronotope/chrono/issues/1486))
##### Documentation
- Correct version number of deprecation notices
([#​1486](https://redirect.github.com/chronotope/chrono/issues/1486))
- Fix some typos
([#​1505](https://redirect.github.com/chronotope/chrono/issues/1505))
- Slightly improve serde documentation
([#​1519](https://redirect.github.com/chronotope/chrono/issues/1519))
- Main documentation: simplify links and reflow text
([#​1535](https://redirect.github.com/chronotope/chrono/issues/1535))
##### Internal
- CI: Lint benchmarks
([#​1489](https://redirect.github.com/chronotope/chrono/issues/1489))
- Remove unnessary `Copy` and `Send` impls
([#​1492](https://redirect.github.com/chronotope/chrono/issues/1492),
thanks [@​erickt](https://redirect.github.com/erickt))
- Backport streamlined `NaiveDate` unit tests
([#​1500](https://redirect.github.com/chronotope/chrono/issues/1500),
thanks [@​Zomtir](https://redirect.github.com/Zomtir))
- Rename `LocalResult` to `TzResolution`, add alias
([#​1501](https://redirect.github.com/chronotope/chrono/issues/1501))
- Update windows-bindgen to 0.55
([#​1504](https://redirect.github.com/chronotope/chrono/issues/1504))
- Avoid duplicate imports, which generate warnings on nightly
([#​1507](https://redirect.github.com/chronotope/chrono/issues/1507))
- Add extra debug assertions to `NaiveDate::from_yof`
([#​1518](https://redirect.github.com/chronotope/chrono/issues/1518))
- Some small simplifications to `DateTime::date_naive` and
`NaiveDate::diff_months`
([#​1530](https://redirect.github.com/chronotope/chrono/issues/1530))
- Remove `unwrap` in Unix `Local` type
([#​1533](https://redirect.github.com/chronotope/chrono/issues/1533))
- Use different method to ignore feature-dependent doctests
([#​1534](https://redirect.github.com/chronotope/chrono/issues/1534))
Thanks to all contributors on behalf of the chrono team,
[@​djc](https://redirect.github.com/djc) and
[@​pitdicker](https://redirect.github.com/pitdicker)!
###
[`v0.4.35`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.35)
[Compare
Source](https://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1234))
- Add getters to `Parsed`
([#​1465](https://redirect.github.com/chronotope/chrono/issues/1465))
##### Deprecations
- Deprecate timestamp methods on `NaiveDateTime`
([#​1473](https://redirect.github.com/chronotope/chrono/issues/1473))
- Deprecate panicking constructors of `TimeDelta`
([#​1450](https://redirect.github.com/chronotope/chrono/issues/1450))
##### Changes/fixes
- Use `NonZeroI32` inside `NaiveDate`
([#​1207](https://redirect.github.com/chronotope/chrono/issues/1207))
- Mark `format::Numeric` and `format::Fixed` as `non_exhaustive`
([#​1430](https://redirect.github.com/chronotope/chrono/issues/1430))
- `Parsed` fixes to error values
([#​1439](https://redirect.github.com/chronotope/chrono/issues/1439))
- Use `overflowing_naive_local` in `DateTime::checked_add*`
([#​1333](https://redirect.github.com/chronotope/chrono/issues/1333))
- Do complete range checks in `Parsed::set_*`
([#​1465](https://redirect.github.com/chronotope/chrono/issues/1465))
##### Documentation
- Rustfmt doctests
([#​1452](https://redirect.github.com/chronotope/chrono/issues/1452))
- Improve docs for crate features
([#​1455](https://redirect.github.com/chronotope/chrono/issues/1455),
thanks [@​edmorley](https://redirect.github.com/edmorley))
- Add more documentation and examples to `Parsed`
([#​1439](https://redirect.github.com/chronotope/chrono/issues/1439))
##### Internal
- Refactor `internals` module
([#​1428](https://redirect.github.com/chronotope/chrono/issues/1428),
[#​1429](https://redirect.github.com/chronotope/chrono/issues/1429),
[#​1431](https://redirect.github.com/chronotope/chrono/issues/1431),
[#​1432](https://redirect.github.com/chronotope/chrono/issues/1432),
[#​1433](https://redirect.github.com/chronotope/chrono/issues/1433),
[#​1438](https://redirect.github.com/chronotope/chrono/issues/1438))
- CI: test cross-compiling to `x86_64-unknown-illumos` instead of
Solaris
([#​1437](https://redirect.github.com/chronotope/chrono/issues/1437))
- CI: lint Windows target, fix clippy warning
([#​1441](https://redirect.github.com/chronotope/chrono/issues/1441))
- CI: only run `cargo hack check` on Linux
([#​1442](https://redirect.github.com/chronotope/chrono/issues/1442))
- Update windows-bindgen to 0.54
([#​1462](https://redirect.github.com/chronotope/chrono/issues/1462),
[#​1483](https://redirect.github.com/chronotope/chrono/issues/1483))
- Simplify error value of `parse_internal`
([#​1459](https://redirect.github.com/chronotope/chrono/issues/1459))
- Simplify `SerdeError`
([#​1458](https://redirect.github.com/chronotope/chrono/issues/1458))
- Simplify `NaiveDate::from_isoywd` a bit
([#​1464](https://redirect.github.com/chronotope/chrono/issues/1464))
Thanks to all contributors on behalf of the chrono team,
[@​djc](https://redirect.github.com/djc) and
[@​pitdicker](https://redirect.github.com/pitdicker)!
###
[`v0.4.34`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.34)
[Compare
Source](https://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1385),
thanks [@​danwilliams](https://redirect.github.com/danwilliams))
- Remove check for `DurationExceedsTimestamp` in `DurationRound`
([#​1403](https://redirect.github.com/chronotope/chrono/issues/1403),
thanks [@​joroKr21](https://redirect.github.com/joroKr21))
- Fix localized formatting with `%X`
([https://github.com/chronotope/pure-rust-locales/pull/12](https://redirect.github.com/chronotope/pure-rust-locales/pull/12),
[#​1420](https://redirect.github.com/chronotope/chrono/issues/1420))
- Windows: base implementation on `GetTimeZoneInformationForYear`
([#​1017](https://redirect.github.com/chronotope/chrono/issues/1017))
##### Additions
- Add `TimeDelta::try_milliseconds`
([#​1385](https://redirect.github.com/chronotope/chrono/issues/1385),
thanks [@​danwilliams](https://redirect.github.com/danwilliams))
- Add `TimeDelta::new`
([#​1337](https://redirect.github.com/chronotope/chrono/issues/1337))
- Add `StrftimeItems::{parse, parse_to_owned}` and more documentation
([#​1184](https://redirect.github.com/chronotope/chrono/issues/1184))
- More standard traits and documentation for `format::Locale` (via
[https://github.com/chronotope/pure-rust-locales/pull/8](https://redirect.github.com/chronotope/pure-rust-locales/pull/8))
##### Changes
- Rename `Duration` to `TimeDelta`, add type alias
([#​1406](https://redirect.github.com/chronotope/chrono/issues/1406))
- Make `TimeDelta` methods const
([#​1337](https://redirect.github.com/chronotope/chrono/issues/1337))
- Make remaining methods of `NaiveDate`, `NaiveWeek`, `NaiveTime` and
`NaiveDateTime` const where possible
([#​1337](https://redirect.github.com/chronotope/chrono/issues/1337))
- Make methods on `DateTime` const where possible
([#​1400](https://redirect.github.com/chronotope/chrono/issues/1400))
- Make `Display` format of `TimeDelta` conform better to ISO 8601
([#​1328](https://redirect.github.com/chronotope/chrono/issues/1328))
##### Documentation
- Fix the formatting of `timestamp_micros`'s Example doc
([#​1338](https://redirect.github.com/chronotope/chrono/issues/1338)
via
[#​1386](https://redirect.github.com/chronotope/chrono/issues/1386),
thanks [@​emikitas](https://redirect.github.com/emikitas))
- Specify branch for GitHub Actions badge and fix link
([#​1388](https://redirect.github.com/chronotope/chrono/issues/1388))
- Don't mention some deprecated methods in docs
([#​1395](https://redirect.github.com/chronotope/chrono/issues/1395))
- Remove stray documentation from main
([#​1397](https://redirect.github.com/chronotope/chrono/issues/1397))
- Improved documentation of `TimeDelta` constructors
([#​1385](https://redirect.github.com/chronotope/chrono/issues/1385),
thanks [@​danwilliams](https://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1390),
[#​1402](https://redirect.github.com/chronotope/chrono/issues/1402)).
- Don't use deprecated method in `impl Arbitrary for DateTime` and set
up CI test
([#​1336](https://redirect.github.com/chronotope/chrono/issues/1336))
- Remove workaround for Rust < 1.61
([#​1393](https://redirect.github.com/chronotope/chrono/issues/1393))
- Bump `codecov/codecov-action` from 3 to 4
([#​1404](https://redirect.github.com/chronotope/chrono/issues/1404))
- Remove partial support for handling `-0000` offset
([#​1411](https://redirect.github.com/chronotope/chrono/issues/1411))
- Move `TOO_LONG` error out of `parse_internal`
([#​1419](https://redirect.github.com/chronotope/chrono/issues/1419))
Thanks to all contributors on behalf of the chrono team,
[@​djc](https://redirect.github.com/djc) and
[@​pitdicker](https://redirect.github.com/pitdicker)!
###
[`v0.4.33`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.33)
[Compare
Source](https://redirect.github.com/chronotope/chrono/compare/v0.4.32...v0.4.33)
This release fixes the broken docrs.rs build of [chrono
0.4.32](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.32).
#### What's Changed
- Make `rkyv` feature imply `size_32`
([#​1383](https://redirect.github.com/chronotope/chrono/issues/1383))
- Fixed typo in `Duration::hours()` exception
([#​1384](https://redirect.github.com/chronotope/chrono/issues/1384),
thanks [@​danwilliams](https://redirect.github.com/danwilliams))
###
[`v0.4.32`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.32)
[Compare
Source](https://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1071))
- Fix out of range panics in `DateTime` getters and setters
([#​1317](https://redirect.github.com/chronotope/chrono/issues/1317),
[#​1329](https://redirect.github.com/chronotope/chrono/issues/1329))
#### Additions
- Add `NaiveDateTime::checked_(add|sub)_offset`
([#​1313](https://redirect.github.com/chronotope/chrono/issues/1313))
- Add `DateTime::to_utc`
([#​1325](https://redirect.github.com/chronotope/chrono/issues/1325))
- Derive `Default` for `Duration`
([#​1327](https://redirect.github.com/chronotope/chrono/issues/1327))
- Add `Duration::subsec_nanos`
([#​1327](https://redirect.github.com/chronotope/chrono/issues/1327))
- Add `try_*` builders to `Duration`
([#​1327](https://redirect.github.com/chronotope/chrono/issues/1327))
- Implement `AddAssign` and `SubAssign` for `Duration`
([#​1327](https://redirect.github.com/chronotope/chrono/issues/1327))
- Make methods on `NaiveDateTime` const where possible
([#​1286](https://redirect.github.com/chronotope/chrono/issues/1286))
- Split `clock` feature into `clock` and `now`
([#​1343](https://redirect.github.com/chronotope/chrono/issues/1343),
thanks [@​mmastrac](https://redirect.github.com/mmastrac))
- Add `From<NaiveDate>` for `NaiveDateTime`
([#​1355](https://redirect.github.com/chronotope/chrono/issues/1355),
thanks [@​dcechano](https://redirect.github.com/dcechano))
- Add `NaiveDateTime::from_timestamp_nanos`
([#​1357](https://redirect.github.com/chronotope/chrono/issues/1357),
thanks
[@​Ali-Mirghasemi](https://redirect.github.com/Ali-Mirghasemi))
- Add `Months::num_months()` and `num_years()`
([#​1373](https://redirect.github.com/chronotope/chrono/issues/1373),
thanks [@​danwilliams](https://redirect.github.com/danwilliams))
- Add `DateTime<Utc>::from_timestamp_millis`
([#​1374](https://redirect.github.com/chronotope/chrono/issues/1374),
thanks [@​xmakro](https://redirect.github.com/xmakro))
#### Changes
- Fix panic in `Duration::MIN.abs()` (adjust `Duration::MIN` by 1
millisecond)
([#​1334](https://redirect.github.com/chronotope/chrono/issues/1334))
- Bump MSRV to 1.61
([#​1347](https://redirect.github.com/chronotope/chrono/issues/1347))
- Update windows-targets requirement from 0.48 to 0.52
([#​1360](https://redirect.github.com/chronotope/chrono/issues/1360))
- Update windows-bindgen to 0.52
([#​1379](https://redirect.github.com/chronotope/chrono/issues/1379))
#### Deprecations
- Deprecate standalone `format` functions
([#​1306](https://redirect.github.com/chronotope/chrono/issues/1306))
#### Documentation
- Improve doc comment and tests for timestamp_nanos_opt
([#​1299](https://redirect.github.com/chronotope/chrono/issues/1299),
thanks [@​mlegner](https://redirect.github.com/mlegner))
- Switch to `doc_auto_cfg`
([#​1305](https://redirect.github.com/chronotope/chrono/issues/1305),
[#​1326](https://redirect.github.com/chronotope/chrono/issues/1326))
- Document panics in `Add`/`Sub` impls and use `expect`
([#​1316](https://redirect.github.com/chronotope/chrono/issues/1316))
- Improve types listed in top-level documentation
([#​1274](https://redirect.github.com/chronotope/chrono/issues/1274))
- Improve deprecation note of `TimeZone::datetime_from_str`
([#​1342](https://redirect.github.com/chronotope/chrono/issues/1342),
thanks [@​tmccombs](https://redirect.github.com/tmccombs))
- Fix typos in `Datelike` impl for `DateTime`
([#​1376](https://redirect.github.com/chronotope/chrono/issues/1376),
thanks [@​ElectrifyPro](https://redirect.github.com/ElectrifyPro))
#### Rkyv support
- Export `Archived*` types in `rkyv` module
([#​1304](https://redirect.github.com/chronotope/chrono/issues/1304))
- Duplicate derives on `Archived*` types
([#​1271](https://redirect.github.com/chronotope/chrono/issues/1271),
thanks [@​Awpteamoose](https://redirect.github.com/Awpteamoose))
- Archive derive of PartialEq for rkyv
([#​959](https://redirect.github.com/chronotope/chrono/issues/959),
thanks [@​mkatychev](https://redirect.github.com/mkatychev))
- Expose rkyv features as features for chrono users
([#​1368](https://redirect.github.com/chronotope/chrono/issues/1368),
thanks [@​gz](https://redirect.github.com/gz))
#### Changes to unstable features
- Don't let `unstable-locales` imply the `alloc` feature
([#​1307](https://redirect.github.com/chronotope/chrono/issues/1307))
- Remove `format::{format_localized, format_item_localized}`
([#​1311](https://redirect.github.com/chronotope/chrono/issues/1311))
- Inline `write_rfc2822_inner`, don't localize
([#​1322](https://redirect.github.com/chronotope/chrono/issues/1322))
#### Internal
- Add benchmark for `DateTime::with_*`
([#​1309](https://redirect.github.com/chronotope/chrono/issues/1309))
- Fix `*_DAYS_FROM_YEAR_0` calculation
([#​1312](https://redirect.github.com/chronotope/chrono/issues/1312))
- Add `NaiveTime::overflowing_(add|sub)_offset`
([#​1310](https://redirect.github.com/chronotope/chrono/issues/1310))
- Rewrite `DateTime::overflowing_(add|sub)_offset`
([#​1069](https://redirect.github.com/chronotope/chrono/issues/1069))
- Tests calling date command `set env LC_ALL`
([#​1315](https://redirect.github.com/chronotope/chrono/issues/1315),
thanks [@​jtmoon79](https://redirect.github.com/jtmoon79))
- Update `deny.toml`
([#​1320](https://redirect.github.com/chronotope/chrono/issues/1320))
- Bump actions/setup-node from 3 to 4
([#​1346](https://redirect.github.com/chronotope/chrono/issues/1346))
- test.yml remove errant `with: node-version`
([#​1352](https://redirect.github.com/chronotope/chrono/issues/1352),
thanks [@​jtmoon79](https://redirect.github.com/jtmoon79))
- CI Linting: Fix missing sources checkout in `toml` job
([#​1371](https://redirect.github.com/chronotope/chrono/issues/1371),
thanks [@​gibbz00](https://redirect.github.com/gibbz00))
- Silence clippy lint for test code with Rust 1.74.0
([#​1362](https://redirect.github.com/chronotope/chrono/issues/1362))
Thanks to all contributors on behalf of the chrono team,
[@​djc](https://redirect.github.com/djc) and
[@​pitdicker](https://redirect.github.com/pitdicker)!
###
[`v0.4.31`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.31)
[Compare
Source](https://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1275))
##### Additions
- Add `DateTime::<Utc>::from_timestamp`
([#​1279](https://redirect.github.com/chronotope/chrono/issues/1279),
thanks [@​demurgos](https://redirect.github.com/demurgos))
- Add `TimeZone::timestamp_micros`
([#​1285](https://redirect.github.com/chronotope/chrono/issues/1285),
thanks [@​emikitas](https://redirect.github.com/emikitas))
- Add `DateTime<Tz>::timestamp_nanos_opt` and
`NaiveDateTime::timestamp_nanos_opt`
([#​1275](https://redirect.github.com/chronotope/chrono/issues/1275))
- Add `UNIX_EPOCH` constants
([#​1291](https://redirect.github.com/chronotope/chrono/issues/1291))
##### Fixes
- Format day of month in RFC 2822 without padding
([#​1272](https://redirect.github.com/chronotope/chrono/issues/1272))
- Don't allow strange leap seconds which are not on a minute boundary
initialization methods
([#​1283](https://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1294),
thanks [@​crepererum](https://redirect.github.com/crepererum))
##### Documentation
- Add more documentation about the RFC 2822 obsolete date format
([#​1267](https://redirect.github.com/chronotope/chrono/issues/1267))
##### Internal
- Remove internal `__doctest` feature and `doc_comment` dependency
([#​1276](https://redirect.github.com/chronotope/chrono/issues/1276))
- CI: Bump `actions/checkout` from 3 to 4
([#​1280](https://redirect.github.com/chronotope/chrono/issues/1280))
- Optimize `NaiveDate::add_days` for small values
([#​1214](https://redirect.github.com/chronotope/chrono/issues/1214))
- Upgrade `pure-rust-locales` to 0.7.0
([#​1288](https://redirect.github.com/chronotope/chrono/issues/1288),
thanks [@​jeremija](https://redirect.github.com/jeremija) wo did
good improvements on `pure-rust-locales`)
Thanks to all contributors on behalf of the chrono team,
[@​djc](https://redirect.github.com/djc) and
[@​pitdicker](https://redirect.github.com/pitdicker)!
###
[`v0.4.30`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.30)
[Compare
Source](https://redirect.github.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://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1268).
##### Additions
- Add `NaiveDate::leap_year`
([#​1261](https://redirect.github.com/chronotope/chrono/issues/1261))
##### Documentation
- Update main documentation from README
([#​1260](https://redirect.github.com/chronotope/chrono/issues/1260),
thanks [@​Stygmates](https://redirect.github.com/Stygmates))
- Add history of relation between chrono and time 0.1 to documentation
([https://github.com/chronotope/chrono/pull/1264](https://redirect.github.com/chronotope/chrono/pull/1264),
[https://github.com/chronotope/chrono/pull/1266](https://redirect.github.com/chronotope/chrono/pull/1266))
- Clarify `Timelike::num_seconds_from_midnight` is a simple mapping
([#​1255](https://redirect.github.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://redirect.github.com/jhpratt)
took over maintenance on the `time` crate and released what amounts to a
new crate as `time` 0.2.
[rust#15934]: https://redirect.github.com/rust-lang/rust/pull/15934
[rust#18832]:
https://redirect.github.com/rust-lang/rust/pull/18832#issuecomment-62448221
[rust#18858]: https://redirect.github.com/rust-lang/rust/pull/18858
[rust#24920]: https://redirect.github.com/rust-lang/rust/pull/24920
[RFC 1040]: https://rust-lang.github.io/rfcs/1040-duration-reform.html
[time#136]: https://redirect.github.com/time-rs/time/issues/136
[chrono#286]: https://redirect.github.com/chronotope/chrono/pull/286
[chrono#478]: https://redirect.github.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://redirect.github.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://redirect.github.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://redirect.github.com/chronotope/chrono/pull/499
[RUSTSEC-2020-0159]:
https://rustsec.org/advisories/RUSTSEC-2020-0159.html
[rust#27970]: https://redirect.github.com/rust-lang/rust/issues/27970
[chrono#677]: https://redirect.github.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://redirect.github.com/chronotope/chrono/pull/1095
Thanks to all contributors on behalf of the chrono team,
[@​djc](https://redirect.github.com/djc) and
[@​pitdicker](https://redirect.github.com/pitdicker)!
###
[`v0.4.29`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.29)
[Compare
Source](https://redirect.github.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://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1254))
#### Deprecations
- Deprecate `TimeZone::datetime_from_str`
([#​1251](https://redirect.github.com/chronotope/chrono/issues/1251))
#### Documentation
- Correct documentation for `FromStr` for `Weekday` and `Month`
([#​1226](https://redirect.github.com/chronotope/chrono/issues/1226),
thanks [@​wfraser](https://redirect.github.com/wfraser))
#### Internal improvements
- Revert "add test_issue\_866"
([#​1238](https://redirect.github.com/chronotope/chrono/issues/1238))
- CI: run tests on `i686` and `wasm32-wasi`
([#​1237](https://redirect.github.com/chronotope/chrono/issues/1237))
- CI: Include doctests for code coverage
([#​1248](https://redirect.github.com/chronotope/chrono/issues/1248))
- Move benchmarks to a separate crate
([#​1243](https://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1240),
backported in
[#​1256](https://redirect.github.com/chronotope/chrono/issues/1256))
Thanks to all contributors on behalf of the chrono team,
[@​djc](https://redirect.github.com/djc) and
[@​pitdicker](https://redirect.github.com/pitdicker)!
###
[`v0.4.28`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.28)
[Compare
Source](https://redirect.github.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://redirect.github.com/chronotope/chrono/issues/1234).
###
[`v0.4.27`](https://redirect.github.com/chronotope/chrono/releases/tag/v0.4.27)
[Compare
Source](https://redirect.github.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://redirect.github.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://redirect.github.com/chronotope/chrono/pull/1175))
#### Additions
- Let `DateTime::signed_duration_since` take argument with `Borrow`
([https://github.com/chronotope/chrono/pull/1119](https://redirect.github.com/chronotope/chrono/pull/1119))
- Implement `PartialOrd` for `Month`
([https://github.com/chronotope/chrono/pull/999](https://redirect.github.com/chronotope/chrono/pull/999),
thanks [@​Munksgaard](https://redirect.github.com/Munksgaard))
- Add `Ord` and `Eq` for types which already derive `PartialOrd` and
`PartialEq`
([https://github.com/chronotope/chrono/pull/1128](https://redirect.github.com/chronotope/chrono/pull/1128),
thanks [@​totikom](https://redirect.github.com/totikom))
- implement `FusedIterator` for `NaiveDateDaysIterator` and
`NaiveDateWeeksIterator`
([https://github.com/chronotope/chrono/pull/1134](https://redirect.github.com/chronotope/chrono/pull/1134))
- Make `NaiveDateDaysIterator` and `NaiveDateWeeksIterator` public
([https://github.com/chronotope/chrono/pull/1134](https://redirect.github.com/chronotope/chrono/pull/1134))
- Add `FromStr` for `FixedOffset`
([https://github.com/chronotope/chrono/pull/1157](https://redirect.github.com/chronotope/chrono/pull/1157),
thanks [@​mcronce](https://redirect.github.com/mcronce))
- Remove `Tz::Offset: Display` requirement from `DateTime::to_rfc*`
([https://github.com/chronotope/chrono/pull/1160](https://redirect.github.com/chronotope/chrono/pull/1160))
- More flexible offset formatting (not exposed yet)
([https://github.com/chronotope/chrono/pull/1160](https://redirect.github.com/chronotope/chrono/pull/1160))
- Make `StrftimeItems` with `unstable-locales` work without allocating
([https://github.com/chronotope/chrono/pull/1152](https://redirect.github.com/chronotope/chrono/pull/1152))
- Make `NaiveDate::from_ymd_opt` const
([https://github.com/chronotope/chrono/pull/1172](https://redirect.github.com/chronotope/chrono/pull/1172),
thanks [@​kamadorueda](https://redirect.github.com/kamadorueda))
- Implement `Error` trait for `ParseWeekdayError` and `ParseMonthError`
([https://github.com/chronotope/chrono/pull/539](https://redirect.github.com/chronotope/chrono/pull/539),
thanks [@​mike-kfed](https://redirect.github.com/mike-kfed))
- Make methods on `NaiveTime` const, update MSRV to 1.57
([https://github.com/chronotope/chrono/pull/1080](https://redirect.github.com/chronotope/chrono/pull/1080))
- Make methods on `NaiveDate` const
([https://github.com/chronotope/chrono/pull/1205](https://redirect.github.com/chronotope/chrono/pull/1205))
- Implement operations for `core::time::Duration` on `DateTime` types
([https://github.com/chronotope/chrono/pull/1229](https://redirect.github.com/chronotope/chrono/pull/1229))
#### Fixes
- Ensure `timestamp_nanos` panics on overflow in release builds
([https://github.com/chronotope/chrono/pull/1123](https://redirect.github.com/chronotope/chrono/pull/1123))
- Fix `offset_from_local_datetime` for `wasm_bindgen`
([https://github.com/chronotope/chrono/pull/1131](https://redirect.github.com/chronotope/chrono/pull/1131))
- Parsing: Consider `%s` to be a timestamp in UTC
([https://github.com/chronotope/chrono/pull/1136](https://redirect.github.com/chronotope/chrono/pull/1136))
- Don't panic when formatting with `%#z`
([https://github.com/chronotope/chrono/pull/1140](https://redirect.github.com/chronotope/chrono/pull/1140),
thanks [@​domodwyer](https://redirect.github.com/domodwyer))
- Parsing: allow MINUS SIGN (U+2212) in offset
([https://github.com/chronotope/chrono/pull/1087](https://redirect.github.com/chronotope/chrono/pull/1087),
thanks [@​jtmoon79](https://redirect.github.com/jtmoon79))
- Fix locale formatting for `%c` and `%r`
([https://github.com/chronotope/chrono/pull/1165](https://redirect.github.com/chronotope/chrono/pull/1165))
- Localize decimal point with `unstable-locales` feature
([https://github.com/chronotope/chrono/pull/1168](https://redirect.github.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://redirect.github.com/chronotope/chrono/pull/1201),
thanks to help from [@​jfro](https://redirect.github.com/jfro))
- Fix deserialization of negative timestamps
([https://github.com/chronotope/chrono/pull/1194](https://redirect.github.com/chronotope/chrono/pull/1194))
- Do not use `Offset`'s `Debug` impl when serializing `DateTime`
([https://github.com/chronotope/chrono/pull/1035](https://redirect.github.com/chronotope/chrono/pull/1035))
- Allow missing seconds in `NaiveTime::from_str`
([https://github.com/chronotope/chrono/pull/1181](https://redirect.github.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://redirect.github.com/chronotope/chrono/pull/1220),
thanks
[@​AlexTMjugador](https://redirect.github.com/AlexTMjugador))
- Small fixes to the RFC 3339 parsers
([https://github.com/chronotope/chrono/pull/1145](https://redirect.github.com/chronotope/chrono/pull/1145))
#### Documentation
- Add "Errors" and "Panics" sections to API docs
([https://github.com/chronotope/chrono/pull/1120](https://redirect.github.com/chronotope/chrono/pull/1120))
- Specify licenses in SPDX format
([https://github.com/chronotope/chrono/pull/1132](https://redirect.github.com/chronotope/chrono/pull/1132),
backport of
[https://github.com/chronotope/chrono/issues/910](https://redirect.github.com/chronotope/chrono/issues/910),
thanks [@​LingMan](https://redirect.github.com/LingMan))
- Fix `NaiveTime` doc typo
([https://github.com/chronotope/chrono/pull/1146](https://redirect.github.com/chronotope/chrono/pull/1146),
thanks [@​zachs18](https://redirect.github.com/zachs18))
- Clarify nanosecond formatting specifier doc
([https://github.com/chronotope/chrono/pull/1173](https://redirect.github.com/chronotope/chrono/pull/1173))
- Add warning against combining multiple `Datelike::with_*`
([https://github.com/chronotope/chrono/pull/1199](https://redirect.github.com/chronotope/chrono/pull/1199)
</details>
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.
👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config
help](https://redirect.github.com/renovatebot/renovate/discussions) if
that's undesired.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/Timmi6790/netcup-offer-bot).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS43LjEiLCJ1cGRhdGVkSW5WZXIiOiIzOS43LjEiLCJ0YXJnZXRCcmFuY2giOiJtYXN0ZXIiLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Timmi6790 <13711365+Timmi6790@users.noreply.github.com>- Loading branch information
1 parent
503057a
commit b3f82d7