chronotope/chrono
### [`v0.4.23`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.23): 0.4.23
[Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.22...v0.4.23)
0.4.23 is the next 0.4 release of the popular chrono date and time library for Rust. After the 0.4.20-0.4.22 series that brought chrono back to life after a long hiatus, development has been fairly quiet, allowing us to start planning changes for the 0.5.0 release. As such, we've started deprecating some APIs that are likely to be removed in 0.5. If you have any feedback on these changes, please let us know in the issue tracker!
##### Deprecations
- Deprecate methods that have an `_opt()` alternative ([#827](https://togithub.com/chronotope/chrono/issues/827))
- Deprecate usage of the `Date` type ([#851](https://togithub.com/chronotope/chrono/issues/851))
##### Features
- Optimize RFC 3339 (and RFC 2822) encoding ([#844](https://togithub.com/chronotope/chrono/issues/844), thanks to [@conradludgate](https://togithub.com/conradludgate))
- Addition and subtraction with the `Days` type ([#784](https://togithub.com/chronotope/chrono/issues/784))
- Add `NaiveDateTime::from_timestamp_millis(_opt)` ([#818](https://togithub.com/chronotope/chrono/issues/818), thanks to [@Pscheidl](https://togithub.com/Pscheidl) -- backported in [#823](https://togithub.com/chronotope/chrono/issues/823))
- Allow for changing TZ variable and cache it for `Local` timezone ([#853](https://togithub.com/chronotope/chrono/issues/853))
- Add optional support for the `arbitrary::Arbitrary` trait ([#849](https://togithub.com/chronotope/chrono/issues/849), thanks to [@greyblake](https://togithub.com/greyblake) and [@asayers](https://togithub.com/asayers))
##### Fixes
- Support tzdb location on AIX ([#826](https://togithub.com/chronotope/chrono/issues/826))
- Fix warnings in documentation ([#847](https://togithub.com/chronotope/chrono/issues/847))
On behalf of [@esheppa](https://togithub.com/esheppa) and [@djc](https://togithub.com/djc), thanks to all contributors!
Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
0.4.22->0.4.230.23.0->0.23.1Release Notes
chronotope/chrono
### [`v0.4.23`](https://togithub.com/chronotope/chrono/releases/tag/v0.4.23): 0.4.23 [Compare Source](https://togithub.com/chronotope/chrono/compare/v0.4.22...v0.4.23) 0.4.23 is the next 0.4 release of the popular chrono date and time library for Rust. After the 0.4.20-0.4.22 series that brought chrono back to life after a long hiatus, development has been fairly quiet, allowing us to start planning changes for the 0.5.0 release. As such, we've started deprecating some APIs that are likely to be removed in 0.5. If you have any feedback on these changes, please let us know in the issue tracker! ##### Deprecations - Deprecate methods that have an `_opt()` alternative ([#827](https://togithub.com/chronotope/chrono/issues/827)) - Deprecate usage of the `DateConfiguration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.