Update Rust crate chrono to 0.4.27 #167
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/chrono-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.4.26->0.4.27Release Notes
chronotope/chrono (chrono)
v0.4.27: 0.4.27Compare Source
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
NaiveDateandNaiveTimeare made const,NaiveDateTimeand others will follow in a later release.Deprecations
DateTime::{from_local, from_utc}(https://github.com/chronotope/chrono/pull/1175)Additions
DateTime::signed_duration_sincetake argument withBorrow(https://github.com/chronotope/chrono/pull/1119)PartialOrdforMonth(https://github.com/chronotope/chrono/pull/999, thanks @Munksgaard)OrdandEqfor types which already derivePartialOrdandPartialEq(https://github.com/chronotope/chrono/pull/1128, thanks @totikom)FusedIteratorforNaiveDateDaysIteratorandNaiveDateWeeksIterator(https://github.com/chronotope/chrono/pull/1134)NaiveDateDaysIteratorandNaiveDateWeeksIteratorpublic (https://github.com/chronotope/chrono/pull/1134)FromStrforFixedOffset(https://github.com/chronotope/chrono/pull/1157, thanks @mcronce)Tz::Offset: Displayrequirement fromDateTime::to_rfc*(https://github.com/chronotope/chrono/pull/1160)StrftimeItemswithunstable-localeswork without allocating (https://github.com/chronotope/chrono/pull/1152)NaiveDate::from_ymd_optconst (https://github.com/chronotope/chrono/pull/1172, thanks @kamadorueda)Errortrait forParseWeekdayErrorandParseMonthError(https://github.com/chronotope/chrono/pull/539, thanks @mike-kfed)NaiveTimeconst, update MSRV to 1.57 (https://github.com/chronotope/chrono/pull/1080)NaiveDateconst (https://github.com/chronotope/chrono/pull/1205)core::time::DurationonDateTimetypes (https://github.com/chronotope/chrono/pull/1229)Fixes
timestamp_nanospanics on overflow in release builds (https://github.com/chronotope/chrono/pull/1123)offset_from_local_datetimeforwasm_bindgen(https://github.com/chronotope/chrono/pull/1131)%sto be a timestamp in UTC (https://github.com/chronotope/chrono/pull/1136)%#z(https://github.com/chronotope/chrono/pull/1140, thanks @domodwyer)%cand%r(https://github.com/chronotope/chrono/pull/1165)unstable-localesfeature (https://github.com/chronotope/chrono/pull/1168)Offset'sDebugimpl when serializingDateTime(https://github.com/chronotope/chrono/pull/1035)NaiveTime::from_str(https://github.com/chronotope/chrono/pull/1181)android-tzdataif theclockfeature is not enabled (https://github.com/chronotope/chrono/pull/1220, thanks @AlexTMjugador)Documentation
NaiveTimedoc typo (https://github.com/chronotope/chrono/pull/1146, thanks @zachs18)Datelike::with_*(https://github.com/chronotope/chrono/pull/1199)Utc::nowandLocal::now(https://github.com/chronotope/chrono/pull/1192)Weekday::num_days_from_monday(https://github.com/chronotope/chrono/pull/1193)Internal improvements
DateTime::to_rfc_*optimizations (https://github.com/chronotope/chrono/pull/1200)format/formatting.rs(https://github.com/chronotope/chrono/pull/1156)saturating_abs(https://github.com/chronotope/chrono/pull/1124)Makefile(https://github.com/chronotope/chrono/pull/1133)wasm-bindgenfeature (https://github.com/chronotope/chrono/pull/1131)try_verify_against_date_command(https://github.com/chronotope/chrono/pull/1161)no_std(https://github.com/chronotope/chrono/pull/1166)test_parse(https://github.com/chronotope/chrono/pull/1170)#test_date_extreme_offset(https://github.com/chronotope/chrono/pull/1195)features-check(https://github.com/chronotope/chrono/pull/1216)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.