fix(deps): update all dependencies #3
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/all"
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:
1.0.71->1.0.810.6.1->0.7.50.4.23->0.4.370.2->1.00.13.0->0.14.01.0.96->1.0.1150.3.4->0.5.20.1.37->0.1.400.3.16->0.3.181.3.0->1.8.0Release Notes
dtolnay/anyhow
v1.0.81Compare Source
v1.0.80Compare Source
v1.0.79Compare Source
v1.0.78Compare Source
v1.0.77Compare Source
anyhow::Error::backtraceavailable on stable Rust compilers 1.65+ (#293, thanks @LukasKalbertodt)v1.0.76Compare Source
unsafe_op_in_unsafe_fnlint (#329)v1.0.75Compare Source
v1.0.74Compare Source
v1.0.73Compare Source
v1.0.72Compare Source
tokio-rs/axum
v0.7.5: axum - v0.7.5Compare Source
axum::servedirectly witha
RouterorMethodRouter(#2586)h2is no longer pulled as a dependency unless thehttp2featureis enabled (#2605)
v0.7.4: axum - v0.7.4Compare Source
debug_handleron tuple response types (#2201)must_useattribute toServeandWithGracefulShutdown(#2484)axum_core::body::BodyDataStreamfrom axumv0.7.3: axum - v0.7.3Compare Source
BodyimplementsFrom<()>now (#2411)tracingfeature by default (#2460)serve(#2398)RouterIntoServiceimplementsClone(#2456)v0.7.2: axum - v0.7.2Compare Source
axum::body::to_bytes(#2373)serve(#2400)v0.7.1: axum - v0.7.1Compare Source
v0.7.0: axum - v0.7.0Compare Source
WebSocketUpgrade::max_send_queue(i.e. the
Btype param has been removed) (#1751 and #1789):FromRequestPartsFromRequestHandlerServiceHandlerWithoutStateExtHandlerLayeredFutureLayeredMethodRouterNextRequestExtRouteFutureRouteRouterhyper::Bodyas that type is removedin hyper 1.0. Instead axum has its own body type at
axum::body::Body(#1751)extract::BodyStreamhas been removed asbody::Bodyimplements
StreamandFromRequestdirectly (#1751)sse::Event::json_datato useaxum_core::Erroras its error type (#1762)DefaultOnFailedUpdgradetoDefaultOnFailedUpgrade(#1664)OnFailedUpdgradetoOnFailedUpgrade(#1664)TypedHeaderhas been move toaxum-extra(#1850)EmptyandFull. Useaxum::body::Body::emptyandaxum::body::Body::fromrespectively (#1789)IntoResponse::into_responsemust useaxum::body::Bodyas the body type.axum::response::Responsedoes this(#1789)
BoxBodytype alias and itsbox_bodyconstructor. Use
axum::body::Body::newinstead (#1789)RawBodyextractor.axum::body::BodyimplementsFromRequestdirectly (#1789)http-bodyno longer implementIntoResponse:Full, useBody::frominsteadEmpty, useBody::emptyinsteadBoxBody, useBody::newinsteadUnsyncBoxBody, useBody::newinsteadMapData, useBody::newinsteadMapErr, useBody::newinsteadaxum::extract::Requesttype alias where the body isaxum::body::Body(#1789)Router::as_serviceandRouter::into_serviceto workaroundtype inference issues when calling
ServiceExtmethods on aRouter(#1835)axum::Serveras it was removed in hyper 1.0. Insteaduse
axum::serve(listener, service)or hyper/hyper-util for more configuration options (#1868)Router::nest.Routers nested with
Router::nest_servicewill no longer inherit fallbacks (#1956)Sec-WebSocket-Keyheader inWebSocketUpgrade(#1972)axum::extract::Query::try_from_uri(#2058)IntoResponseforBox<str>andBox<[u8]>([#2035])MethodFilter. It no longer uses bitflags (#2073).source()of composite rejections (#2030)#[debug_handler](#2014)IntoResponsefor(R,) where R: IntoResponse(#2143)NestedPathextractor (#1924)handle_errorfunction to existingServiceExttrait (#2235)impl<T> IntoResponse(Parts) for Extension<T>now requiresT: Clone, as that is required by the http crate (#1882)axum::Json::from_bytes(#2244)FromRequestPartsforhttp::request::Parts(#2328)FromRequestPartsforhttp::Extensions(#2328)DefaultBodyLimitto individual routes (#2157)v0.6.20: axum - v0.6.20Compare Source
WebSocketUpgrade::write_buffer_sizeandWebSocketUpgrade::max_write_buffer_sizeWebSocketUpgrade::max_send_queueHandlerforT: IntoResponse(#2140)v0.6.19: axum - v0.6.19Compare Source
axum::extract::Query::try_from_uri(#2058)IntoResponseforBox<str>andBox<[u8]>(#2035).source()of composite rejections (#2030)#[debug_handler](#2014)v0.6.18: axum - v0.6.18Compare Source
Sec-WebSocket-Keyheader inWebSocketUpgrade(#1972)v0.6.17: axum - v0.6.17Compare Source
CONNECTrequests (#1958)v0.6.16: axum - v0.6.16Compare Source
MatchedPathin fallbacks (#1934)Routerwith something nested at/was used as a fallback (#1934)Router::new().fallback(...)isn't optimal (#1940)v0.6.15: axum - v0.6.15Compare Source
v0.6.14: axum - v0.6.14Compare Source
v0.6.13: axum - v0.6.13Compare Source
axum::rejection=tracetarget (#1890)Router::nestintroduced in0.6.0.
nestnow flattens the routes which performs better (#1711)MatchedPathin nested handlers now gives the fullmatched path, including the nested path (#1711)
DerefandDerefMutfor built-in extractors (#1922)v0.6.12: axum - v0.6.12Compare Source
IntoResponseforMultipartError(#1861)v0.6.11: axum - v0.6.11Compare Source
S: Debugforimpl Debug for Router<S>(#1836)v0.6.10: axum - v0.6.10Compare Source
#[must_use]attributes to types that do nothing unless used (#1809)TypedHeaderextractor (#1810)Routervia a dynamic library (#1806)v0.6.9: axum - v0.6.9Compare Source
v0.6.8: axum - v0.6.8Compare Source
Allowmissing from routers with middleware (#1773)KeepAlive::eventfor customizing the event sent for SSE keep alive (#1729)v0.6.7: axum - v0.6.7Compare Source
FormRejection::FailedToDeserializeFormBodywhich is returnedif the request body couldn't be deserialized into the target type, as opposed
to
FailedToDeserializeFormwhich is only for query parameters (#1683)MockConnectInfofor settingConnectInfoduring tests (#1767)v0.6.6: axum - v0.6.6Compare Source
MethodRoutertoRouter::fallback(#1730)v0.6.5: axum - v0.6.5Compare Source
#[debug_handler]sometimes giving wrong borrow related suggestions (#1710)impl IntoResponseas the return type from handler functions (#1736)v0.6.4: axum - v0.6.4Compare Source
v0.6.3: axum - v0.6.3Compare Source
IntoResponsefor&'static [u8; N]and[u8; N](#1690)Pathsupport types usingserde::Deserializer::deserialize_any(#1693)RawPathParams(#1713)CloneandServiceforaxum::middleware::Next(#1712)v0.6.2: axum - v0.6.2Compare Source
body_textandstatusmethods to built-in rejections (#1612)runtimefeature ofhyperwhen usingtokio(#1671)chronotope/chrono
v0.4.37Compare Source
Version 0.4.36 introduced an unexpected breaking change and was yanked. In it
LocalResultwas renamed toMappedLocalTimeto avoid the impression that it is aResulttype 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 nameMappedLocalTimethe 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 from yesterday for the yanked release.
v0.4.36Compare Source
This release un-deprecates the methods on
TimeDeltathat 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:Additions
DateTime::with_time()(#1510)Deprecations
TimeDeltadeprecations (#1543)TimeStamp::timestamp_subsec_nanos, which was missed in the 0.4.35 release (#1486)Documentation
Internal
CopyandSendimpls (#1492, thanks @erickt)NaiveDateunit tests (#1500, thanks @Zomtir)LocalResulttoTzResolution, add alias (#1501)NaiveDate::from_yof(#1518)DateTime::date_naiveandNaiveDate::diff_months(#1530)unwrapin UnixLocaltype (#1533)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.35Compare Source
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. TheNaiveDateTimetype 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 theDateTime<Utc>type, or from theTimeZonetrait.Converting from
NaiveDateTimetoDateTime<Utc>is simple with.and_utc(), and in the other direction with.naive_utc().The panicking constructors of
TimeDelta(the new name of theDurationtype) 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
NaiveDatenow includes a niche. So nowOption<NaiveDate>,Option<NaiveDateTime>andOption<DateTime<Tz>>are the same size as their base types.format::Numericandformat::Fixedare marked asnon_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
DateTime::{from_timestamp_micros, from_timestamp_nanos}(#1234)Parsed(#1465)Deprecations
NaiveDateTime(#1473)TimeDelta(#1450)Changes/fixes
NonZeroI32insideNaiveDate(#1207)format::Numericandformat::Fixedasnon_exhaustive(#1430)Parsedfixes to error values (#1439)overflowing_naive_localinDateTime::checked_add*(#1333)Parsed::set_*(#1465)Documentation
Parsed(#1439)Internal
internalsmodule (#1428, #1429, #1431, #1432, #1433, #1438)x86_64-unknown-illumosinstead of Solaris (#1437)cargo hack checkon Linux (#1442)parse_internal(#1459)SerdeError(#1458)NaiveDate::from_isoywda bit (#1464)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.34Compare Source
Notable changes
Durationtype toTimeDelta. This removes the confusion between chrono's type and the laterDurationtype in the standard library. It will remain available under the old name as a type alias for compatibility.Localis 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.Displayformat ofTimeDeltais 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
TimeDelta::milliseconds(#1385, thanks @danwilliams)DurationExceedsTimestampinDurationRound(#1403, thanks @joroKr21)%X(https://github.com/chronotope/pure-rust-locales/pull/12, #1420)GetTimeZoneInformationForYear(#1017)Additions
TimeDelta::try_milliseconds(#1385, thanks @danwilliams)TimeDelta::new(#1337)StrftimeItems::{parse, parse_to_owned}and more documentation (#1184)format::Locale(via https://github.com/chronotope/pure-rust-locales/pull/8)Changes
DurationtoTimeDelta, add type alias (#1406)TimeDeltamethods const (#1337)NaiveDate,NaiveWeek,NaiveTimeandNaiveDateTimeconst where possible (#1337)DateTimeconst where possible (#1400)Displayformat ofTimeDeltaconform better to ISO 8601 (#1328)Documentation
timestamp_micros's Example doc (#1338 via #1386, thanks @emikitas)TimeDeltaconstructors (#1385, thanks @danwilliams)Internal
mainbranch, work on 0.5 happens in the0.5.xbranch (#1390, #1402).impl Arbitrary for DateTimeand set up CI test (#1336)codecov/codecov-actionfrom 3 to 4 (#1404)-0000offset (#1411)TOO_LONGerror out ofparse_internal(#1419)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.33Compare Source
This release fixes the broken docrs.rs build of chrono 0.4.32.
What's Changed
rkyvfeature implysize_32(#1383)Duration::hours()exception (#1384, thanks @danwilliams)v0.4.32Compare Source
In this release we shipped part of the effort to reduce the number of methods that could unexpectedly panic, notably for the
DateTimeandDurationtypes.Chrono internally stores the value of a
DateTimein UTC, and transparently converts it to the local value as required. For example adding a second to aDateTimeneeds 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 forDebugoutput.In chrono 0.4.32 the range of
NaiveDate,NaiveDateTimeandDateTimeis 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 theMINandMAXdates.Durationhad a similar issue. The range of this type was pretty arbitrary picked to match the range of ani64in milliseconds. Negating ani64::MINpushes a value out of range, and in the same way negatingDuration::MINcould 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::MAXinstead and prevent the panic case.Other highlights:
Durationgained new fallible initialization methods.rkyv.NaiveDateTimeare now const.DateTimeconst in a future release.Complete list of changes:
Fixes
TimeZone::from_local_datetime(#1071)DateTimegetters and setters (#1317, #1329)Additions
NaiveDateTime::checked_(add|sub)_offset(#1313)DateTime::to_utc(#1325)DefaultforDuration(#1327)Duration::subsec_nanos(#1327)try_*builders toDuration(#1327)AddAssignandSubAssignforDuration(#1327)NaiveDateTimeconst where possible (#1286)clockfeature intoclockandnow(#1343, thanks @mmastrac)From<NaiveDate>forNaiveDateTime(#1355, thanks @dcechano)NaiveDateTime::from_timestamp_nanos(#1357, thanks @Ali-Mirghasemi)Months::num_months()andnum_years()(#1373, thanks @danwilliams)DateTime<Utc>::from_timestamp_millis(#1374, thanks @xmakro)Changes
Duration::MIN.abs()(adjustDuration::MINby 1 millisecond) (#1334)Deprecations
formatfunctions (#1306)Documentation
doc_auto_cfg(#1305, #1326)Add/Subimpls and useexpect(#1316)TimeZone::datetime_from_str(#1342, thanks @tmccombs)Datelikeimpl forDateTime(#1376, thanks @ElectrifyPro)Rkyv support
Archived*types inrkyvmodule (#1304)Archived*types (#1271, thanks @Awpteamoose)Changes to unstable features
unstable-localesimply theallocfeature (#1307)format::{format_localized, format_item_localized}(#1311)write_rfc2822_inner, don't localize (#1322)Internal
DateTime::with_*(#1309)*_DAYS_FROM_YEAR_0calculation (#1312)NaiveTime::overflowing_(add|sub)_offset(#1310)DateTime::overflowing_(add|sub)_offset(#1069)set env LC_ALL(#1315, thanks @jtmoon79)deny.toml(#1320)with: node-version(#1352, thanks @jtmoon79)tomljob (#1371, thanks @gibbz00)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.31Compare Source
Another maintenance release.
It was not a planned effort to improve our support for UNIX timestamps, yet most PRs seem related to this.
Deprecations
timestamp_nanosin favor of the non-panickingtimestamp_nanos_opt(#1275)Additions
DateTime::<Utc>::from_timestamp(#1279, thanks @demurgos)TimeZone::timestamp_micros(#1285, thanks @emikitas)DateTime<Tz>::timestamp_nanos_optandNaiveDateTime::timestamp_nanos_opt(#1275)UNIX_EPOCHconstants (#1291)Fixes
This makes many methods a little more strict:
NaiveTime::from_hms_milliNaiveTime::from_hms_milli_optNaiveTime::from_hms_microNaiveTime::from_hms_micro_optNaiveTime::from_hms_nanoNaiveTime::from_hms_nano_optNaiveTime::from_num_seconds_from_midnightNaiveTime::from_num_seconds_from_midnight_optNaiveDate::and_hms_milliNaiveDate::and_hms_milli_optNaiveDate::and_hms_microNaiveDate::and_hms_micro_optNaiveDate::and_hms_nanoNaiveDate::and_hms_nano_optNaiveDateTime::from_timestampNaiveDateTime::from_timestamp_optTimeZone::timestampTimeZone::timestamp_optNaiveDateTime::timestamp_nanos_opt(#1294, thanks @crepererum)Documentation
Internal
__doctestfeature anddoc_commentdependency (#1276)actions/checkoutfrom 3 to 4 (#1280)NaiveDate::add_daysfor small values (#1214)pure-rust-localesto 0.7.0 (#1288, thanks @jeremija wo did good improvements onpure-rust-locales)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.30Compare Source
In this release, we have decided to swap out the
chrono::Durationtype (which has been a re-export of time 0.1Durationtype) with our own definition, which exposes a strict superset of thetime::DurationAPI. This helps avoid warnings about the CVE-2020-26235 and RUSTSEC-2020-0071 advisories for downstream users and allows us to improve theDurationAPI 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 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.
Additions
NaiveDate::leap_year(#1261)Documentation
Timelike::num_seconds_from_midnightis a simple mapping (#1255)Relation between chrono and time 0.1
Rust first had a
timemodule added tostdin its 0.7 release. It later moved tolibextra, and then to alibtimelibrary 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::Durationwas included asstd::time::Duration(rust#15934) in 2014.In preparation of Rust 1.0 at the end of 2014
libtimewas moved out of the Rust distro and into thetimecrate to eventually be redesigned (rust#18832, rust#18858), like thenumandrandcrates. Of course chrono kept its dependency on thistimecrate.timestarted re-exportingstd::time::Durationduring this period. Later, the standard library was changed to have a more limited unsignedDurationtype (rust#24920, RFC 1040), while thetimecrate kept the full functionality withtime::Duration.time::Durationhad been a part of chrono's public API.By 2016
time0.1 lived under therust-lang-deprecatedorganisation and was not actively maintained (time#136). chrono absorbed the platform functionality andDurationtype of thetimecrate in chrono#478 (the work started in chrono#286). In order to preserve compatibility with downstream crates depending ontimeandchronosharing aDurationtype, chrono kept depending on time 0.1. chrono offered the option to opt out of thetimedependency by disabling theoldtimefeature (swapping it out for an effectively similar chrono type). In 2019, @jhpratt took over maintenance on thetimecrate and released what amounts to a new crate astime0.2.Security advisories
In November of 2020 CVE-2020-26235 and RUSTSEC-2020-0071 were opened against the
timecrate. @quininer had found that calls tolocaltime_rmay 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 totime.On Unix-like systems a process is given a timezone id or description via the
TZenvironment 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.time0.1 and chrono used the POSIX functionlocaltime_rto do the conversion to local time, which reads theTZvariable.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
getenvin 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 theTZvariable or viaiana-time-zoneas 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. As such, chrono now respects the Rust lock when reading theTZenvironment variable. In general, code should avoid modifying the environment.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::Durationtype, 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
Durationimplementation 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.Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.29Compare Source
This release fixes a panic introduced in chrono 0.4.27 in
FromStr<DateTime<Utc>>(#1253).Chrono now has a Discord channel.
Fixes
parse_rfc3339_relaxed(#1254)Deprecations
TimeZone::datetime_from_str(#1251)Documentation
FromStrforWeekdayandMonth(#1226, thanks @wfraser)Internal improvements
i686andwasm32-wasi(#1237)This allows us to upgrade the criterion dependency to 5.1 without changing our MSRV.
Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.28Compare Source
This release fixes a test failure on 32-bit targets introduced with 0.4.27, see https://github.com/chronotope/chrono/issues/1234.
v0.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.The parser for the
%+formatting specifier and theRFC3339formatting item is switched from a strict to a relaxed parser (see https://github.com/chronotope/chrono/pull/1145). This matches the existing documentation, and the parser used byDateTime::from_str. If you need to validate the input, consider usingDateTime::from_rfc3339.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!
v0.4.26Compare Source
The changes from #807 we merged for 0.4.25 unfortunately restricted parsing in a way that was incompatible with earlier 0.4.x releases. We reverted this in #1113. A small amount of other changes were merged since.
DurationRoundpanics from issue #1010 (#1093, thanks to @pitdicker)Thanks on behalf of the chrono team (@djc and @esheppa) to all contributors!
v0.4.25: 0.4.25Compare Source
Time for another maintenance release. This release bumps the MSRV to 1.56; given MSRV bumps in chrono's dependencies (notably for syn 2), we felt that it no longer made sense to support any older versions. Feedback welcome in our issue tracker!
Additions
NaiveDateTime::and_utc()method (#952, thanks to @klnusbaum)Hashfor most pub types that also derivePartialEq(#938, thanks to @bruceg)parse_and_remainder()methods (#1011, thanks to @pitdicker)DateTime::fix_offset()(#1030, thanks to @pitdicker)#[track_caller]toLocalResult::unwrap(#1046, thanks to @pitdicker)#[must_use]to some methods (#1007, thanks to @aceArt-GmbH)PartialOrdforMonth(#999, thanks to @Munksgaard)impl From<NaiveDateTime> for NaiveDate(#1012, thanks to @pezcore)Fixes
NaiveWeek::last_day(#1070, thanks to @pitdicker)LocaltoFixedOffset(#1041, thanks to @pitdicker)Refactoring
Local(#992, thanks to @nekevss)Documentation
Internal improvements
clockfeature (#1061, thanks to @pitdicker)--no-default-features(#1059, thanks to @pitdicker)bench_year_flags_from_yearfrom being optimized out (#1034, thanks to @pitdicker)test_datetime_parse_from_str(#1078, thanks to @pitdicker)set -eux, use bash (#1103, thanks to @jtmoon79)LANGtocin gnudate(#1089, thanks to @scarf005)TryFrom(#1086, thanks to @pitdicker)On behalf of @djc and @esheppa, thanks to all contributors!
v0.4.24: 0.4.24Compare Source
This is a small maintenance release with accumulated fixes and improvements.
Days::new()to refer to days, not months (#874, thanks to @brotskydotcom)from_timestamp_opt()(#879, thanks to @xmo-odoo)format_localized()forNaiveDate(#881, thanks to @mseele)Add/SubDays, add tests with DST timezone (#878)NaiveTime::MINpublic (#890)from_timestamp_millis()implementation and add more tests (#885)from_timestamp_micros()function (#906, thanks to @umanwizard)Hashfor most pub types that also derivePartialEq(#938, thanks to @bruceg)from_utc()example (#939, thanks to @greg-el)DateTime::checked_add_days()(#942, thanks to @Ekleog)FixedOffsetdocs (#953, thanks to @klnusbaum)const(#984, thanks to @tormeh)Thanks to all contributors from the chrono team, @esheppa and @djc.
iamcodemaker/console_log
v1.0.0Compare Source
This is a re-release of v0.2.2. There have been no major code changes for over two years. Let's call it stable. 🎉
Full Changelog: https://github.com/iamcodemaker/console_log/compare/0.2.2...1.0.0
v0.2.2What's Changed
New Contributors
This is the first time generating release notes, so not all of these contributions are in this release. I still wanted to recognize the contributions.
Full Changelog: https://github.com/iamcodemaker/console_log/commits/0.2.2
graphql-rust/graphql-client
v0.14.0Compare Source
extend typedirectivegraphqls://schemagenerate_module_token_stream_from_stringto allow custom macro wrappersserde-rs/json
v1.0.115Compare Source
v1.0.114Compare Source
v1.0.113Compare Source
swap_removeandshift_removemethods on Map (#1109)v1.0.112Compare Source
v1.0.111Compare Source
v1.0.110Compare Source
v1.0.109Compare Source
v1.0.108Compare Source
v1.0.107Compare Source
v1.0.106Compare Source
Value::as_numberaccessor (#1069, thanks @chanced)Number::as_straccessor under "arbitrary_precision" feature (#1067, thanks @chanced)v1.0.105Compare Source
v1.0.104Compare Source
v1.0.103Compare Source
v1.0.102Compare Source
v1.0.101Compare Source
v1.0.100Compare Source
-Z minimal-versionsv1.0.99Compare Source
v1.0.98Compare Source
v1.0.97Compare Source
io_error_kind()method to serde_json::Error:fn io_error_kind(&self) -> Option<std::io::ErrorKind>(#1026)tower-rs/tower-http
v0.5.2: v0.5.2Compare Source
Added:
vary: accept-encodingheader on compressed responses (#399)x-gzipas equivalent togzipinaccept-encodingrequest header (#467)Fixed
v0.5.1: v0.5.1Compare Source
zstdinServeFileResponseBodyandResponseFuture(#455)HttpMakeClassifierandGrpcMakeClassifier(#455)Fixed
ServeDirnow no longer redirects from/directoryto/directory/if
append_index_html_on_directoriesis disabled (#421)v0.5.0: v0.5.0Compare Source
Changed
Fixed
http-range-header to
0.4v0.4.4: v0.4.4Compare Source
v0.4.3: v0.4.3Compare Source
Fixed
v0.4.2: v0.4.2Compare Source
Added
DefaultforDecompressionBody(#370)Changed
Fixed
v0.4.1: v0.4.1Compare Source
Added
DefaultforMakeRequestUuid(#335)DefaultforServeFileSystemResponseBody(#336)Fixed
Accept-Encodingrequest header (#220)multiple_membersforGzipDecoder(#354)v0.4.0: v0.4.0Compare Source
Added
RequestDecompressionmiddleware (#282)DefaultforCompressionBody(#323)Changed
ServeDirandServeFile's error types are nowInfallibleand any IO errorswill be converted into responses. Use
try_callto generate error responses manually (BREAKING) (#283)ServeDir::fallbackandServeDir::not_found_servicenow requiresthe fallback service to use
Infallibleas its error type (BREAKING) (#283)Removed
RequireAuthorizationin favor ofValidateRequest(BREAKING) (#290)Fixed
ServeDir, convertio::ErrorKind::NotADirectoryto404 Not Found(#331)v0.3.5: v0.3.5Compare Source
Added
NormalizePathmiddleware (#275)ValidateRequestmiddleware (#289)RequestBodyTimeoutmiddleware (#303)Changed
Fixed
on_responsecallback (#278)*) is passed toAllowOrigin::list. UseAllowOrigin::any()instead (#285)tokio-rs/tracing
v0.1.40: tracing 0.1.40Compare Source
This release fixes a potential stack use-after-free in the
Instrument::into_innermethod. Only uses of this method are affected by thisbug.
Fixed
mem::ManuallyDropinstead ofmem::forgetinInstrument::into_inner(#2765)
Thanks to @cramertj and @manishearth for finding and fixing this issue!
v0.1.39: tracing 0.1.39Compare Source
This release adds several additional features to the
tracingmacros. Inaddition, it updates the
tracing-coredependency to v0.1.32 andthe
tracing-attributesdependency to v0.1.27.Added
ValueSets of any length (#2508)Changed
tracing-attributes: updated to 0.1.27tracing-core: updated to 0.1.32Fixed
(#2621, #2757)
clippy::let_with_type_underscore] in macro-generatedcode ([#2609])
unknown_lintsin macro-generated code (#2626)#[instrument]when the"log"feature is enabled (#2599)
Documented
axum-insightsto relevant crates. (#2713)clippy-tracingto related crates (#2628)tracing-cloudwatchto related crates (#2667)tracing-etwrepo (#2602)v0.1.38: tracing 0.1.38Compare Source
This
tracingrelease changes theDropimplementation forInstrumentedFutures so that the attachedSpanis entered when dropping theFuture. Thismeans that events emitted by the
Future'sDropimplementation will now berecorded within its
Span. It also adds#[inline]hints to methods called inthe
event!macro's expansion, for an improvement in both binary size andperformance.
Additionally, this release updates the
tracing-attributesdependency tov0.1.24, which updates the [
syn][syn] dependency to v2.x.x.tracing-attributesv0.1.24 also includes improvements to the#[instrument]macro; see the
tracing-attributes0.1.24 release notes fordetails.
Added
Instrumentedfutures will now enter the attachedSpanin theirDropimplementation, allowing events emitted when dropping the future to occur
within the span (#2562)
#[inline]attributes for methods called by theevent!macros, makinggenerated code smaller (#2555)
levelargument to#[instrument(err)]and#[instrument(ret)]to override the level ofthe generated return value event (#2335)
#[instrument]is added to aconst fn(#2418)
Changed
tracing-attributes: updated to 0.1.24cfg-ifdependency (#2553)syn][syn] dependency to 2.0 (#2516)Fixed
clippy::unreachablewarnings in#[instrument]-generated code (#2356)syndependency (#2530)Documented
#[instrument(err)](#2433)#[instrument](#2350)Thanks to @nitnelave, @jsgf, @Abhicodes-crypto, @LukeMathWalker, @andrewpollack,
@quad, @klensy, @davidpdrsn, @dbidwell94, @ldm0, @NobodyXu, @ilsv, and @daxpedda
for contributing to this release!
uuid-rs/uuid
v1.8.0Compare Source
⚠️ Potential Breakage ⚠️
A new
impl AsRef<Uuid> for Uuidbound has been added, which can break inference on code like:You can fix these by explicitly typing the result of the conversion:
or by calling
as_bytesinstead:What's Changed
wasm-bindgenas a dependency onwasm32-unknown-unknownby @emilk in https://github.com/uuid-rs/uuid/pull/738New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.7.0...1.8.0
v1.7.0Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.6.1...1.7.0
v1.6.1Compare Source
What's Changed
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.6.0...1.6.1
v1.6.0Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.5.0...1.6.0
v1.5.0Compare Source
What's Changed
bytemucksupport by @John-Toohey in https://github.com/uuid-rs/uuid/pull/711New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.4.1...1.5.0
v1.4.1Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.4.0...1.4.1
v1.4.0Compare Source
What's Changed
borshsupport by @grovesNL in https://github.com/uuid-rs/uuid/pull/686New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.3.4...1.4.0
v1.3.4Compare Source
What's Changed
wasm32-wasisupport with tests by @acfoltzer in https://github.com/uuid-rs/uuid/pull/677New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.3.3...1.3.4
v1.3.3Compare Source
What's Changed
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.3.2...1.3.3
v1.3.2Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.3.1...1.3.2
v1.3.1Compare Source
What's Changed
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.3.0...1.3.1
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: Cargo.lock