chore(deps): update all dependencies #2
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.890.6.18->0.7.00.4.26->0.4.384.3.4->4.5.170.6->0.81.28.2->1.40.0Release Notes
dtolnay/anyhow (anyhow)
v1.0.89Compare Source
UnwindSafeandRefUnwindSafeimpl consistently available between versions of Rust newer and older than 1.72 (#386)v1.0.88Compare Source
v1.0.87Compare Source
Error::newandError::chain, in no-std mode on Rust 1.81+ (#383)v1.0.86Compare Source
ensure!with non-literal after minus sign (#373)v1.0.85Compare Source
ensure!macro's rules to unblock some rustc pretty-printer improvements (#368, #371)v1.0.84Compare Source
ensure!through aNotimpl for a type that is notbool(#367)v1.0.83Compare Source
v1.0.82Compare Source
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 (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)chronotope/chrono (chrono)
v0.4.38Compare Source
This release bring a ca. 20% improvement to the performance of the formatting code, and a convenient
days_sincemethod for theWeekdaytype.Chrono 0.4.38 also removes the long deprecated
rustc-serializefeature. Support forrustc-serializewill be soft-destabilized in the next Rust edition. 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)forDateTimeinstead of a manual implementation. It is reverted in this release.Removals
rustc-serializefeature (#1548, thanks @workingjubilee)Additions
Weekday::days_since(#1249, based on #216 by @clarfonthey)TimeDelta::checked_mulandTimeDelta::checked_div(#1565, thanks @Zomtir)Fixes
CopyforDateTimeif offset isCopy(#1573)Internal
test_encodable_jsonandtest_decodable_jsonfunctions (#1550)cargo hack check(#1553)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
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!
clap-rs/clap (clap)
v4.5.17Compare Source
Fixes
v4.5.16Compare Source
Fixes
derivefeature is missingv4.5.15Compare Source
Compatiblity
Arg::removechanged return typesFixes
Arg::removereturn the removed itemv4.5.14Compare Source
Features
Arg::addfor attaching arbitrary state, like completion hints, toArgwithoutArgknowing about itv4.5.13Compare Source
Fixes
#[flatten]ing an optional#[group(skip)]v4.5.12Compare Source
v4.5.11Compare Source
v4.5.10Compare Source
v4.5.9Compare Source
Fixes
v4.5.8Compare Source
Fixes
v4.5.7Compare Source
Fixes
num_argsv4.5.6Compare Source
v4.5.5Compare Source
Fixes
exclusiveto overriderequired_unless_present,required_unless_present_any,required_unless_present_allv4.5.4Compare Source
Fixes
#[arg(id)]attributes againv4.5.3Compare Source
Internal
heckv4.5.2Compare Source
Fixes
v4.5.1Compare Source
Fixes
v4.5.0Compare Source
Compatibility
v4.4.18Compare Source
Fixes
usagefeature, ensure the list of required arguments is uniquev4.4.17Compare Source
Fixes
panic!when mixingargs_conflicts_with_subcommandswithArgGroup(which is implicit withderive) introduced in 4.4.15v4.4.16Compare Source
Fixes
v4.4.15Compare Source
Fixes
args_conflicts_with_subcommandsargs_conflicts_with_subcommandswhen using subcommand short and long flagsv4.4.14Compare Source
Documentation
findcookbook entry to allow repeats of flags/optionsFeatures
num_args(0)on options which allows making them emulate being a flag for position-tracking flagsv4.4.13Compare Source
Documentation
v4.4.12Compare Source
Performance
TypedValueParserfor possible values if neededv4.4.11Compare Source
Features
Command::mut_groupv4.4.10Compare Source
Documentation
v4.4.9Compare Source
Fixes
Command::aboutunder flattened headingshidewhen flattening subcommandsv4.4.8Compare Source
Features
Command::flatten_helpto allowgit stash -hlike help for subcommandsv4.4.7Compare Source
Performance
v4.4.6Compare Source
Internal
anstreamv4.4.5Compare Source
Fixes
nameorlong_flag, allow ambiguous-looking matches that unambiguously map back to the same commandlong_flag, don't panicv4.4.4Compare Source
Internal
terminal_sizeto 0.3v4.4.3Compare Source
Documentation
v4.4.2Compare Source
Performance
once_celldependencyv4.4.1Compare Source
Fixes
usagefeature, ensure the list of required arguments is uniquev4.4.0Compare Source
compatibility
v4.3.24Compare Source
Fixes
--helpwith custom templatesv4.3.23Compare Source
Fixes
UnknownArgumentValueParserto not error on flag's absencev4.3.22Compare Source
Features
UnknownArgumentValueParserfor injecting errors for improving the experience with errorsv4.3.21Compare Source
Features
TryMapValueParserso the type can be namedv4.3.20Compare Source
Features
Command::mut_argsfor modifying all arguments en massev4.3.19Compare Source
Fixes
value_terminatoreven in the presence of later multiple-value positional argumentsv4.3.18Compare Source
Fixes
--in fewer places where it won't workv4.3.17Compare Source
Fixes
PossibleValuedescriptions in--helpv4.3.16Compare Source
Fixes
v4.3.15Compare Source
Features
anstyleDocumentation
v4.3.14Compare Source
Features
ArgAction::HelpShortandArgAction::HelpLongfor explicitly specifying which style of help to displayFixes
[OPTIONS]in usage if a help or versionArgActionis usedv4.3.13Compare Source
v4.3.12Compare Source
Fixes
v4.3.11Compare Source
Features
num::Wrapping,Box, orArcBox<str>,Box<OsStr>, andBox<Path>v4.3.10Compare Source
Performance
v4.3.9Compare Source
Fixes
Command::ignore_errorsno longer masks help/versionv4.3.8Compare Source
Fixes
infer_long_arg, rather than arbitrarily picking one, matching the documentation and subcommand's behaviorv4.3.7Compare Source
Documentation
v4.3.6Compare Source
Documentation
cliov4.3.5Compare Source
ColorChoice::possible_valuesis added to simplify things for builder usersFixes
ColorChoice::to_possible_valueno longer includes descriptions, encouraging shorter help where possiblelaunchbadge/sqlx (sqlx)
v0.8.2Compare Source
10 pull requests were merged this release cycle.
This release addresses a few regressions that have occurred, and refines SQLx's MSRV policy (see the FAQ).
Added
Changed
Fixed
v0.8.1Compare Source
16 pull requests were merged this release cycle.
This release contains a fix for RUSTSEC-2024-0363.
Postgres users are advised to upgrade ASAP as a possible exploit has been demonstrated:
#3440 (comment)
MySQL and SQLite do not appear to be exploitable, but upgrading is recommended nonetheless.
Added
Changed
Fixed
v0.8.0Compare Source
70 pull requests were merged this release cycle.
#2697 was merged the same day as release 0.7.4 and so was missed by the automatic CHANGELOG generation.
Breaking
Added
Changed
Fixed
clockandstdfeatures ofworkspace.dependencies.chrono.v0.7.4Compare Source
38 pull requests were merged this release cycle.
This is officially the last release of the 0.7.x release cycle.
As of this release, development of 0.8.0 has begun on
mainand only high-priority bugfixes may be backported.Added
Changed
Fixed
v0.7.338 pull requests were merged this release cycle.
Added
Changed
Fixed
v0.7.223 pull requests were merged this release cycle.
Added
Changed
Fixed
v0.7.1Compare Source
This release mainly addresses issues reported with the 0.7.0 release.
16 pull requests were merged this release cycle.
Added
Changed
Fixed
v0.7.0Compare Source
At least 70 pull requests were merged this release cycle! (The exact count is muddied with pull requests for alpha
releases and such.) And we gained 43 new contributors! Thank you to everyone who helped make this release a reality.
Breaking
Many revisions were made to query analysis in the SQLite driver; these are all potentially breaking changes
as they can change the output of
sqlx::query!()et al. We'd like to thank [[@tyrelr]] for their numerous PRs tothis area.
The MSSQL driver has been removed as it was not nearly at the same maturity level as the other drivers.
As previously announced, we have plans to introduce a fully featured replacement as a premium offering,
alongside drivers for other proprietary databases, with the goal to support full-time development on SQLx.
If interested, please email your inquiry to sqlx@launchbadge.com.
The offline mode for the queries has been changed to use a separate file per
query!()invocation,which is intended to reduce the number of conflicts when merging branches in a project that both modified queries.
This means that CLI flag
--mergedis no longer supported. See [#2363] for details and make sure that yoursqlx-cliversion is in sync with thesqlxversion in your project.The type ascription override syntax for the query macros has been deprecated,
as parse support for it has been removed in
syn 2.0, which we'll be upgrading to in the next breaking release.This can be replaced with type overrides using casting syntax (
as).See [#2483] for details.
Added
Changed
Fixed
tokio-rs/tokio (tokio)
v1.40.0: Tokio v1.40.0Compare Source
1.40.0 (August 30th, 2024)
Added
util::SimplexStream(#6589)Command::process_group(#6731){TrySendError,SendTimeoutError}::into_inner(#6755)JoinSet::join_all(#6784)Added (unstable)
Builder::{on_task_spawn, on_task_terminate}(#6742)Changed
write_all_bufwhen possible (#6724)UnwindSafe(#6783)SleepandBatchSemaphoreinstrumentation explicit roots (#6727)NonZeroU64fortask::Id(#6733)JoinError(#6753)#[must_use]toJoinHandle::abort_handle(#6762)Documented
[build]section doesn't go in Cargo.toml (#6728)select!(#6774)v1.39.3: Tokio v1.39.3Compare Source
1.39.3 (August 17th, 2024)
This release fixes a regression where the unix socket api stopped accepting the abstract socket namespace. (#6772)
v1.39.2: Tokio v1.39.2Compare Source
1.39.2 (July 27th, 2024)
This release fixes a regression where the
select!macro stopped accepting expressions that make use of temporary lifetime extension. (#6722)v1.39.1: Tokio v1.39.1Compare Source
1.39.1 (July 23rd, 2024)
This release reverts "time: avoid traversing entries in the time wheel twice" because it contains a bug. (#6715)
v1.39.0: Tokio v1.39.0Compare Source
1.39.0 (July 23rd, 2024)
Added
AsyncSeekforEmpty(#6663)num_alive_tasks(#6619, #6667)Command::as_std_mut(#6608)watch::Sender::same_channel(#6637){Receiver,UnboundedReceiver}::{sender_strong_count,sender_weak_count}(#6661)Defaultforwatch::Sender(#6626)CloneforAbortHandle(#6621)consume_budget(#6622)Changed
ReadBuf::put_slice()(#6629)copy_bidirectionalandcopy(#6532)num_cpuswithavailable_parallelism(#6709)block_on(#6692)IntoFuturewithtimeout(#6666)IntoFuturewithjoin!andselect!(#6710)Fixed
Interval(#6612)Added (unstable)
unhandled_panicbehavior for#[tokio::main]and#[tokio::test](#6593)spawned_tasks_count(#6114)worker_park_unpark_count(#6696)Documented
tokio::io::stdoutdocumentation (#6674)join.rsandtry_join.rs(#6641)unhandled_panic(#6660)JoinSet::try_join_nextwhen all tasks are running (#6671)v1.38.1: Tokio v1.38.1Compare Source
1.38.1 (July 16th, 2024)
This release fixes the bug identified as (#6682), which caused timers not
to fire when they should.
Fixed
wake_upwhile holding all the locks of sharded time wheels (#6683)v1.38.0: Tokio v1.38.0Compare Source
This release marks the beginning of stabilization for runtime metrics. It
stabilizes
RuntimeMetrics::worker_count. Future releases will continue tostabilize more metrics.
Added
File::create_new(#6573)copy_bidirectional_with_sizes(#6500)AsyncBufReadforJoin(#6449)CloneforNamedPipeInfo(#6586)Notify::notify_last(#6520)mpsc::Receiver::{capacity,max_capacity}(#6511)splitmethod to the semaphore permit (#6472, #6478)tokio::task::join_set::Builder::spawn_blocking(#6578)Changed
#[tokio::test]append#[test]at the end of the attribute list (#6497)blocking_threadscount (#6551)RuntimeMetrics::worker_count(#6556)lifo_slotinblock_in_place(#6596)global_queue_intervalis zero (#6445)Semaphorefor task dumps (#6499)LocalKey::getwork with Clone types (#6433)true_whenfield inTimerShared(#6563)Fixed
Interval::poll_tick(#6487)is_emptyon mpsc block boundaries (#6603)Documented
stdindocumentation (#6581)ReadHalf::unsplit()documentation (#6498)select!(#6468)NamedPipeServerexample (#6590)SemaphorePermit,OwnedSemaphorePermit(#6477)Barrier::waitis not cancel safe (#6494)watch::Sender::{subscribe,closed}(#6490)spawn_blockingtasks (#6571)LocalSet::run_until(#6599)v1.37.0: Tokio v1.37.0Compare Source
1.37.0 (March 28th, 2024)
Added
set_max_buf_sizetotokio::fs::File(#6411)try_newandtry_with_interesttoAsyncFd(#6345)forget_permitsmethod to semaphore (#6331)is_closed,is_empty, andlento mpsc receivers (#6348)rwlock()method to ownedRwLockguards (#6418)Cloneforwatch::Sender(#6388)TaskLocalFuture::take_value(#6340)FromIteratorforJoinSet(#6300)Changed
io::splituse a mutex instead of a spinlock (#6403)Fixed
Documented
AsyncBufReadExt::fill_buf(#6431)AsyncReadExt's primitive read functions (#6337)Runtimeto#[tokio::main](#6366)enterexample deterministic (#6351)mpsc::Sender::downgradewith#[must_use](#6326)const_newbeforenew_with(#6392)Changed (unstable)
Idin taskdumps (#6328)unhandled_panicis enabled when not supported (#6410)v1.36.0: Tokio v1.36.0Compare Source
1.36.0 (February 2nd, 2024)
Added
tokio::io::Join(#6220)AsyncWriteforEmpty(#6235)UnixSocket(#6290)TcpSocket(#6311){Receiver,UnboundedReceiver}::poll_recv_many(#6236)Sender::{try_,}reserve_many(#6205)watch::Receiver::mark_unchanged(#6252)JoinSet::try_join_next(#6280)Changed
copycooperative (#6265)repeatandsinkcooperative (#6254)Documented
clear_readydocs (#6304)*Fdtraits onTcpSocketare unix-only (#6294)tokio::sync::Mutex(#6279)v1.35.1: Tokio v1.35.1Compare Source
1.35.1 (December 19, 2023)
This is a forward part of a change that was backported to 1.25.3.
Fixed
tokio::runtime::io::registration::async_io(#6221)v1.35.0: Tokio v1.35.0Compare Source
1.35.0 (December 8th, 2023)
Added
Changed
Sizedrequirements fromAsyncReadExt.read_buf(#6169)Runtimeunwind safe (#6189)Fixed
--cfg docsrswork without net feature (#6166)unsync_loadon miri (#6179)Documented
AsyncWriteExtexamples (#6149)LocalSet::run_until(#6147)v1.34.0: Tokio v1.34.0Compare Source
Fixed
clear_readinessafter io driver shutdown (#6067)take(#6080)broadcast::channellink (#6100)Changed
::corequalified imports instead of::stdinsidetokio::testmacro (#5973)Added
fs::read_dirto includeaix(#6075)mpsc::Receiver::recv_many(#6010)v1.33.0: Tokio v1.33.0Compare Source
1.33.0 (October 9, 2023)
Fixed
Interest::addwith#[must_use](#6037)watch::Receiver::wait_for(#6021)spawn_localsource location (#5984)Changed
watch(#6018)Added
tokio::fs::File(#5958)Interest::removemethod (#5906)DuplexStream(#5985)?Sizedbound to{MutexGuard,OwnedMutexGuard}::map(#5997)watch::Receiver::mark_unseen(#5962, #6014, #6017)watch::Sender::new(#5998)OnceCell::from_value(#5903)Removed
statsfeature (#5952)Documented
Child::waitis cancel safe (#5977)Semaphore(#5939, #5956, #5978, #6031, #6032, #6050)broadcastcapacity is a lower bound (#6042)const_newis not instrumented (#6002)mpsc::Sender::send(#5947)watchchannel (#5954)Unstable
v1.32.1: Tokio v1.32.1Compare Source
1.32.1 (December 19, 2023)
This is a forward part of a change that was backported to 1.25.3.
Fixed
tokio::runtime::io::registration::async_io(#6221)v1.32.0: Tokio v1.32.0Compare Source
Fixed
broadcast::Receiver(#5925)Added
Command::raw_arg(#5930)Unstable
v1.31.0: Tokio v1.31.0Compare Source
Fixed
WriteHalf::poll_write_vectored(#5914)Unstable
v1.30.0: Tokio v1.30.0Compare Source
1.30.0 (August 9, 2023)
This release bumps the MSRV of Tokio to 1.63. (#5887)
Changed
--cfg mio_unsupported_force_poll_pollflag (#5881)const_newmethods always available (#5885)Added
broadcast::Sender::new(#5824)UCredfor espidf (#5868)File::options()(#5869)Interval(#5878){ChildStd*}::into_owned_{fd, handle}(#5899)Removed
tokio_*cfgs (#5890)Documented
broadcast::send(#5820)AsyncReadExt::read_exact(#5863)Sleepas!Unpinin docs (#5916)raw_argnot showing up in docs (#5865)Unstable
v1.29.1: Tokio v1.29.1Compare Source
Fixed
block_in_placewith ablock_onbetween (#5837)v1.29.0: Tokio v1.29.0Compare Source
Technically a breaking change, the
Sendimplementation is removed fromruntime::EnterGuard. This change fixes a bug and should not impact most users.Breaking
EnterGuardshould not beSend(#5766)Fixed
fs::read_dir(#5653)JoinSet(#5693)EnterGuarddropped incorrect order (#5772)File(#5803)Changed
Added
broadcast::Receiver::blocking_recv(#5690)raw_argmethod toCommand(#5704)JoinSet::poll_join_next(#5721)Unstable
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 artifacts 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
File name: Cargo.lock
614275f8d5to4b53fc21a74b53fc21a7to3c6e6c76673c6e6c7667tof804b33070f804b33070to3c16adf58a3c16adf58atofabc70bd31fabc70bd31tocfe21690aacfe21690aatoa57270c286a57270c286toebfdfe541eebfdfe541etobaceaf990abaceaf990ato7bc33d44877bc33d4487toe68a110b33e68a110b33toce086980f4ce086980f4tod8c2626919d8c2626919toed2eb3cad2ed2eb3cad2toe3ae519648e3ae519648to3bf6c521a73bf6c521a7to42366da19542366da195to6b5271a86c6b5271a86ctoe1e5ee4b59e1e5ee4b59toa45900d272a45900d272to63fc7c4c2063fc7c4c20tobefe7feb62befe7feb62to072e778d3e072e778d3eto373fc93319373fc93319to76aa3353cf76aa3353cfto1f06d4be981f06d4be98tob2cc47b903b2cc47b903to02789d118702789d1187toa847a2b5e9a847a2b5e9to5b050e4abc5b050e4abctob269e54f1eb269e54f1eto94d02d96a294d02d96a2toeaf435406eeaf435406etoae4b63dda3ae4b63dda3toe2752866e4e2752866e4toc85594ef6bc85594ef6bto05e816447905e8164479to59198e7fb359198e7fb3to543287c07f543287c07ftof21ab17d87f21ab17d87toc3f7d14b89c3f7d14b89to72bb56d9f372bb56d9f3tod33b1919fad33b1919fato83bac0f23683bac0f236to0e358aa3e40e358aa3e4toeea0ce98d9eea0ce98d9to7f39a640ca7f39a640catoa353d1a004a353d1a004tofea7fb49c0⚠️ Artifact update problem
Renovate failed to update artifacts 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
File name: Cargo.lock
fea7fb49c0to19f5c9180819f5c91808to6dcafd3fa76dcafd3fa7to1bfb85dfdb1bfb85dfdbto2ea0d9c65b2ea0d9c65btoe0d8cb19ebe0d8cb19ebto19f3dd7df619f3dd7df6to9b18e35a789b18e35a78to7938d19e4e7938d19e4eto55dcdb53ca55dcdb53cato5d279b05f15d279b05f1toed0df1b468ed0df1b468to067f4ac5eb067f4ac5ebtob1787bbd08b1787bbd08to59e8b79a3a59e8b79a3atodc724123f2dc724123f2to9afc3e59309afc3e5930toc7d67d9778c7d67d9778to07119373220711937322to404707bf5a404707bf5atoc29263e628c29263e628to746e5a30e1746e5a30e1to9a8addca8f9a8addca8ftoc233f0a77bc233f0a77bto053ef2f822053ef2f822to8e44deb41c8e44deb41ctob74cdc32e5b74cdc32e5tob7cd81cb34b7cd81cb34to5d89d2f63e5d89d2f63etocf763e456ecf763e456eto02e2ff184902e2ff1849to69eb1f0ad769eb1f0ad7to4748ba2fff4748ba2ffftodec992f0b4dec992f0b4to4b209d795e4b209d795eto4c5357c2b84c5357c2b8to0fd6cf1a260fd6cf1a26to50f0f725cc50f0f725ccto5ba19466c95ba19466c9toab32af45e3ab32af45e3toa794e3ef71a794e3ef71to31514c615a31514c615ato7a52b0090d7a52b0090dtoca267acd54ca267acd54to261a106521261a106521to0fbebcd7240fbebcd724to6dd34341fe6dd34341fetod3d9cecf27d3d9cecf27toa21d4268eda21d4268edtod9423e7b8bd9423e7b8bto64b8ee6c9c64b8ee6c9ctod0c2ddbf10d0c2ddbf10todc049e83f0dc049e83f0todead4ebfafdead4ebfafto949077241f949077241ftof912d7ad24f912d7ad24to8379bba31f8379bba31ftoe0b51da71de0b51da71dto4f0c83fb334f0c83fb33tof61315ad87f61315ad87to8e7f0a109b8e7f0a109bto9f508316d69f508316d6tocebc808442cebc808442to6041b3e9126041b3e912to8ec7a5420b8ec7a5420bto3d07f52f8a3d07f52f8atoe70beb5ba8e70beb5ba8to9d1d8eca179d1d8eca17to12d1c6ca7b12d1c6ca7bto15023a00da15023a00dato58ff60ecac58ff60ecactoeb3c71859aeb3c71859ato56ca98b07656ca98b076to37f63200fb37f63200fbto2137d10bf12137d10bf1toe2210531fde2210531fdto95c965ead195c965ead1toeb5d09944eeb5d09944etoa7edc6d80fa7edc6d80ftof877658d9af877658d9ato401ba3657c401ba3657ctoc4017f4c95c4017f4c95to60dd1e922860dd1e9228toc3f0f8f47cc3f0f8f47cto05cab17d6c05cab17d6ctoa280b434aaa280b434aatoe965a52be6e965a52be6tocb76d20bffcb76d20bfftofe3394bbbafe3394bbbatobd30117e31bd30117e31to3057bae7f03057bae7f0todf9c90b08edf9c90b08eto3d833495a73d833495a7to0a21fc28cf0a21fc28cfto4979b1a4ff4979b1a4ffto90776ffe4990776ffe49to4da741dc954da741dc95tod8e404fec5d8e404fec5to742903040f742903040fto7973ff2d3a7973ff2d3ato494a4adb64494a4adb64to6193c7af486193c7af48to611aea9282611aea9282to3bc717bbaa3bc717bbaato96f81b0b9e96f81b0b9eto172fa45e76172fa45e76to09248e4fe809248e4fe8to0dad38324e0dad38324etode715a72fede715a72fetoa60d753ae1a60d753ae1to3be6f368db3be6f368dbto0b782707910b78270791to6042dfec766042dfec76to91f9fed4fc91f9fed4fctof766ab4edff766ab4edftof6831644f0f6831644f0toc1c811ff8fc1c811ff8fto39877dc9d739877dc9d7tobb3bdac3c9bb3bdac3c9to79b1d9e69e79b1d9e69eto8a3e2a6b058a3e2a6b05to93a667a37193a667a371tobf864c0afbbf864c0afbto67609214fe67609214fetobbd242a68dbbd242a68dto7922e576ab7922e576abto64ede2028f64ede2028ftob9315dd8b9b9315dd8b9tod79de2b55ed79de2b55eto35a99b9b5735a99b9b57to1a8896f02b1a8896f02btod767292a71d767292a71to5ccf73d71f5ccf73d71ftoafd14c46ddafd14c46ddto27d0c1dbde27d0c1dbdeto8a18d051f08a18d051f0to5e126086345e12608634toab981e36d4ab981e36d4todabd6cda76dabd6cda76tod1ce682a90d1ce682a90tob4d0448eb9b4d0448eb9to3b190a3ec93b190a3ec9to69331fb9d069331fb9d0to4642e2e4364642e2e436to93d9f8a09893d9f8a098to5d02971c285d02971c28to7cd68c5a977cd68c5a97toc2fde97eaec2fde97eaeto5f798823075f79882307toc142c83efec142c83efeto3c65212f3b3c65212f3btoe5f656e547e5f656e547to7df86ddcbd7df86ddcbdtoe82cf14774e82cf14774to2bb1fcc2152bb1fcc215to05db1c5eac05db1c5eacto62404fdd0b62404fdd0bto6a72bf13086a72bf1308tof20ca552e9f20ca552e9to9fcff60e759fcff60e75tod7081c1eead7081c1eeato48a4b25ff548a4b25ff5todcff2a68bfdcff2a68bfto9643de444c9643de444cto7e4cd4c3f67e4cd4c3f6to80a1bdb3b180a1bdb3b1to02f563b7e102f563b7e1tob248ffc5edb248ffc5edtocd6c613a34cd6c613a34to259890e8cf259890e8cftoc80281ed53c80281ed53to6e57cd0e796e57cd0e79tof2eca5a6d7f2eca5a6d7to0c5d34f0150c5d34f015to353be64b20353be64b20toea13ce857eea13ce857eto203201daa7203201daa7toeee867a747eee867a747to5aba7b2da45aba7b2da4to0e7ae465660e7ae46566toedaf7fd7bcedaf7fd7bcto492d771df0492d771df0to49a55291bf49a55291bfto4b219d42044b219d4204to3fb7b772083fb7b77208to5a537e94ee5a537e94eeto3706a171153706a17115toc1bfd14962c1bfd14962to45b413d91745b413d917to54fdeb731654fdeb7316toa8ee5c23a7a8ee5c23a7to3383fb4f5e3383fb4f5eto335afbfa2b335afbfa2bto2ffd291e062ffd291e06toec7634c3e3ec7634c3e3to0a0d8227650a0d822765to569519d744569519d744to8523b7f7228523b7f722to8ca9f3939f8ca9f3939fto80adc77a8b80adc77a8btoce362d3ed7ce362d3ed7to1d280de4091d280de409tobb04223e14bb04223e14to94c10d918094c10d9180tod5c8d96c83d5c8d96c83to913f153717913f153717to4c8b7f55264c8b7f5526to66e52048ff66e52048ffto4ff3d82f9b4ff3d82f9btoa5832e83b5a5832e83b5tocd9d19a2d2cd9d19a2d2to42a6dc1b6542a6dc1b65toa05d448ea2a05d448ea2to62c552ecdc62c552ecdctob8607bb0f6b8607bb0f6toce4cca58efce4cca58efto1a4351286c1a4351286cto19568571f419568571f4toc2159bf6cec2159bf6ceto29bbc8122a29bbc8122atob8a328b526b8a328b526to8cbcb2305d8cbcb2305dto06e84bc1e506e84bc1e5to5cf38ff3275cf38ff327to8ae70c26358ae70c2635toa6d25acff2a6d25acff2to4b2173ea974b2173ea97to12792642d312792642d3to57a4d8614057a4d86140to2b6d9528d92b6d9528d9tofbd8526accfbd8526acctoa340852ef1a340852ef1to1fae648e791fae648e79toe689eb39a4e689eb39a4to7d49fd95687d49fd9568to4d504c44184d504c4418toa3eb588d23a3eb588d23to2d392bf3d22d392bf3d2to144a168b9e144a168b9etod52304481cd52304481cto77f1af17bf77f1af17bfto6503bec8756503bec875tof7305feb1bf7305feb1btobfae7c9cb5bfae7c9cb5toaaaf096feaaaaf096featobd4cf46d8dbd4cf46d8dto0c4683553a0c4683553atoa23eba0f47a23eba0f47tobcecf7cec6bcecf7cec6to2af94e5e582af94e5e58toc3ddb5f3ffc3ddb5f3fftoca0ff854e9ca0ff854e9toab960e4485ab960e4485to4673878ade4673878adeto6e2f21204b6e2f21204btoeeada4701ceeada4701cto48ec68516848ec685168to70cb6beadd70cb6beaddto61b51fad8e61b51fad8etoc459a833f7c459a833f7to120969e68d120969e68dtofbe62aa483fbe62aa483to1701e230571701e23057tobd3787c9e7bd3787c9e7to8b6b981f398b6b981f39to26d74cf4f126d74cf4f1toa6dfe50307a6dfe50307to626931e7be626931e7beto6712ada3c46712ada3c4to5e01cd3b3c5e01cd3b3ctob2ce1d86c3b2ce1d86c3to50ebd7d19350ebd7d193toa4f4921a47a4f4921a47toc94702721bc94702721btoe3d2f7fe95e3d2f7fe95tofad586ab5ffad586ab5ftocf3b52116acf3b52116ato26dfdf244326dfdf2443to8ecf5ee5eb8ecf5ee5ebto60927559236092755923to3f0899f8a23f0899f8a2to6aa1449ade6aa1449adetoae15e3abdfae15e3abdfto0d92a057750d92a05775to3d2f43f9a13d2f43f9a1tofe34e04bb5fe34e04bb5to672fa30bda672fa30bdato2a3b9034222a3b903422to36948753e436948753e4tob37603dee0b37603dee0todd31cf3e6edd31cf3e6eto514b2ab795514b2ab795to582dfa7bb5582dfa7bb5toee17b7e3bcee17b7e3bcto37fca9ea1537fca9ea15toe4c1cae120e4c1cae120tob2ecaa03a3b2ecaa03a3to842a01b0f3842a01b0f3to4db8bdc4464db8bdc446to71b81b8fbe71b81b8fbeto5389570bab5389570babtof6e018d8e1f6e018d8e1toe4e96980a1e4e96980a1tod590f28b2bd590f28b2btof7e0cd890ef7e0cd890eto388149f2ed388149f2edto47bcf1d69647bcf1d696todcfc1c18d2dcfc1c18d2to8e765022228e76502222to60d821035660d8210356to6b701bfb9f6b701bfb9fto8a90de16f68a90de16f6tode06aeb581de06aeb581to1c8d4d42001c8d4d4200toe28bae579de28bae579dto49e69b94c949e69b94c9to045547f1d2045547f1d2to4a742668974a74266897to92aef4e8c392aef4e8c3tobb2a1f0222bb2a1f0222to8f019cd4e28f019cd4e2to11185d060e11185d060eto20d91b0f8f20d91b0f8ftof89d067409f89d067409to54bb7692bb54bb7692bbto427a49cf0e427a49cf0etoaa254e5a27aa254e5a27tof02faf7a99f02faf7a99to0d457054420d45705442to8edd8285a18edd8285a1to153a50ee11153a50ee11to150eb9c389150eb9c389to6e45b5bb8a6e45b5bb8ato17a4a0954617a4a09546to406e31a3a3406e31a3a3toa84b656530a84b656530to7b85eb591a7b85eb591ato1d0fa86d6a1d0fa86d6ato5ac08629275ac0862927tod7f924608cd7f924608ctoa951c990dda951c990ddtoc7c5009510c7c5009510toba2fe0f225ba2fe0f225tob9539032ffb9539032fftofe45bde3fefe45bde3feto5bda2424c05bda2424c0tocf8eb23331cf8eb23331tod333fcc7b6d333fcc7b6to8fd9a0b8a98fd9a0b8a9to80247bad1680247bad16to2adf1054b42adf1054b4to9f8989b7659f8989b765tod6b2930b91d6b2930b91to2081de26e52081de26e5to7a1cab93217a1cab9321tob25c61e09fb25c61e09ftoc5224dc66dc5224dc66dtoff78bd3932ff78bd3932toa9e22dcb0ea9e22dcb0etod00ab4f1c5d00ab4f1c5to1b67a1871f1b67a1871fto5cf9e9ab3f5cf9e9ab3fto3021923cf73021923cf7to21a7579b4e21a7579b4eto5a11c5b2925a11c5b292to4f50bcffbd4f50bcffbdto3ae36217343ae3621734to3a7e12371c3a7e12371cto628e862dca628e862dcato38c48d7d1438c48d7d14to9823fa2c0d9823fa2c0dto613b2f799d613b2f799dto4abfef8a954abfef8a95to6dfd11d6db6dfd11d6dbto9537fc10e69537fc10e6to7b9a464f2b7b9a464f2btoe00c3a3bbfe00c3a3bbfto90369d42d290369d42d2to88271b469b88271b469bto7f22fb57477f22fb5747toe067642897e067642897todc282e23b1dc282e23b1to9b86825acb9b86825acbto1463582bf51463582bf5to22177708322217770832to917e57dc15917e57dc15to34ad0561c934ad0561c9to64d21efb5864d21efb58tof67c60b5adf67c60b5adto2b8bd53e3e2b8bd53e3eto1823906b8d1823906b8dto63ff2edf6f63ff2edf6fto64f03c776564f03c7765to2ed8bc40772ed8bc4077to397a349e83397a349e83to8a876bf0568a876bf056tof5bf7a8d37f5bf7a8d37tod19bac34dad19bac34datoc716a5c079c716a5c079to33fcb53a6c33fcb53a6cto6342d19afa6342d19afatod89828c2eed89828c2eetodcab563c9adcab563c9ato5eaddda3c15eaddda3c1toef971b5985ef971b5985to3c5be158113c5be15811to5dc08ec4335dc08ec433to5ae185faea5ae185faeatoae162bed64ae162bed64toa7ee6e1cd8a7ee6e1cd8to0b3b95f9c00b3b95f9c0tobd189f0d45bd189f0d45toc94ee419cdc94ee419cdto570520b111570520b111to7353c361447353c36144to15a98fa81815a98fa818to5880b3bc7d5880b3bc7dtoc58b15907cc58b15907cto2c86e9b0042c86e9b004to7d0e6f77577d0e6f7757to8712dc24238712dc2423to8fca81971f8fca81971ftoec736a8167ec736a8167tof7278b89fef7278b89feto598657be46598657be46to47eaf6412c47eaf6412ctoffb212ae9dffb212ae9dto993f0b13a3993f0b13a3tob89624ce4ab89624ce4atoc92750acaec92750acaeto8e7ea7be2f8e7ea7be2ftob735289585b735289585to3d5364c5303d5364c530tod2c9105c88d2c9105c88to59b260304159b2603041toe60f68111be60f68111btoe528a8a35ce528a8a35ctoc9edb40f7ec9edb40f7etobcdbbf3a9cbcdbbf3a9cto141d9fd8f5141d9fd8f5to0bc2e5b4280bc2e5b428toefb2b3f364efb2b3f364to521c410db5521c410db5to6f9e20fc3a6f9e20fc3ato4b100fd3f84b100fd3f8toc97aa228eac97aa228eatof80cb152f8f80cb152f8tod899751d08d899751d08to0fb11b8c410fb11b8c41to85be41aba585be41aba5toa5cde7035aa5cde7035atof2d0388769f2d0388769tod2c68beab2d2c68beab2tobd629f8ed4bd629f8ed4to697d07b939697d07b939to88b207c4d688b207c4d6toaf8208ee40af8208ee40tof0a59b90f6f0a59b90f6tobad71da886bad71da886to1d7cb1eda81d7cb1eda8toa3ffd5e9dfa3ffd5e9dftoa0feee0beea0feee0beeto0b56f057ca0b56f057catoc5dbe5ce8fc5dbe5ce8ftobfe5db9d94bfe5db9d94to93c9726ee993c9726ee9tod136523634d136523634to60a88ceb4560a88ceb45to92bb292bca92bb292bcato72b7b3473872b7b34738to908a8b32ed908a8b32edto8b84cdad688b84cdad68to0ba4e25de40ba4e25de4to037a3a5a1f037a3a5a1ftoe2bf7514cbe2bf7514cbtob925db69d0b925db69d0toe0acef5fa5e0acef5fa5toa994c6cec3a994c6cec3to9aa63ba0c39aa63ba0c3to12f857f22c12f857f22cto4d24b469804d24b46980toe40b69cffae40b69cffato431aecb08c431aecb08cto4b5821e7574b5821e757toe1854594d7e1854594d7to2a9bc353662a9bc35366to49e7e552c549e7e552c5to2af0f56d9b2af0f56d9bto9397eb5cd09397eb5cd0to2203d32b152203d32b15to2389ad0bfc2389ad0bfctodde8d70e47dde8d70e47tob09428a1dcb09428a1dcto8eddb86ddd8eddb86dddto54438e936554438e9365to36e281434a36e281434ato7a83b0eef77a83b0eef7toc369329f3ac369329f3atoce1563f082ce1563f082toa3efc25d68a3efc25d68to0e4258e52a0e4258e52ato11099311cf11099311cfto7049232fdb7049232fdbto20ec510f4e20ec510f4etobf3ae6525bbf3ae6525btoaefa5dc636aefa5dc636to645ec9652cCheckout
From your project repository, check out a new branch and test the changes.