chore(deps): update all dependencies #6
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v3
->v4
v3
->v4
v3
->v4
v3
->v4
0.54.1
->1.0.0
0.24.0
->1.0.0
0.54.4
->0.60.0
0.4.24
->0.4.38
4.1.8
->4.5.4
4.0.0
->5.0.0
0.18.0
->0.21.0
^20.1.1
->^24.0.0
1.0.39
->1.0.61
1.26.0
->1.38.0
Release Notes
actions/checkout (actions/checkout)
v4
Compare Source
actions/download-artifact (actions/download-artifact)
v4
Compare Source
actions/setup-node (actions/setup-node)
v4
Compare Source
actions/upload-artifact (actions/upload-artifact)
v4
Compare Source
chronotope/chrono (chrono)
v0.4.38
Compare Source
This release bring a ca. 20% improvement to the performance of the formatting code, and a convenient
days_since
method for theWeekday
type.Chrono 0.4.38 also removes the long deprecated
rustc-serialize
feature. Support forrustc-serialize
will 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)
forDateTime
instead of a manual implementation. It is reverted in this release.Removals
rustc-serialize
feature (#1548, thanks @workingjubilee)Additions
Weekday::days_since
(#1249, based on #216 by @clarfonthey)TimeDelta::checked_mul
andTimeDelta::checked_div
(#1565, thanks @Zomtir)Fixes
Copy
forDateTime
if offset isCopy
(#1573)Internal
test_encodable_json
andtest_decodable_json
functions (#1550)cargo hack check
(#1553)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.37
Compare Source
Version 0.4.36 introduced an unexpected breaking change and was yanked. In it
LocalResult
was renamed toMappedLocalTime
to avoid the impression that it is aResult
type were some of the results are errors. For backwards compatibility a type alias with the old name was added.As it turns out there is one case where a type alias behaves differently from the regular enum: you can't import enum variants from a type alias with
use chrono::LocalResult::*
. With 0.4.37 we make the new nameMappedLocalTime
the alias, but keep using it in function signatures and the documentation as much as possible.See also the release notes of chrono 0.4.36 from yesterday for the yanked release.
v0.4.36
Compare Source
This release un-deprecates the methods on
TimeDelta
that were deprecated with the 0.4.35 release because of the churn they are causing for the ecosystem.New is the
DateTime::with_time()
method. As an example of when it is useful:Additions
DateTime::with_time()
(#1510)Deprecations
TimeDelta
deprecations (#1543)TimeStamp::timestamp_subsec_nanos
, which was missed in the 0.4.35 release (#1486)Documentation
Internal
Copy
andSend
impls (#1492, thanks @erickt)NaiveDate
unit tests (#1500, thanks @Zomtir)LocalResult
toTzResolution
, add alias (#1501)NaiveDate::from_yof
(#1518)DateTime::date_naive
andNaiveDate::diff_months
(#1530)unwrap
in UnixLocal
type (#1533)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.35
Compare 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. TheNaiveDateTime
type doesn't know the offset from UTC, so it was technically wrong to have these methods. The alternative is to use the similar methods on theDateTime<Utc>
type, or from theTimeZone
trait.Converting from
NaiveDateTime
toDateTime<Utc>
is simple with.and_utc()
, and in the other direction with.naive_utc()
.The panicking constructors of
TimeDelta
(the new name of theDuration
type) are deprecated. This was the last part of chrono that defaulted to panicking on error, dating from before rust 1.0.A nice change is that
NaiveDate
now includes a niche. So nowOption<NaiveDate>
,Option<NaiveDateTime>
andOption<DateTime<Tz>>
are the same size as their base types.format::Numeric
andformat::Fixed
are 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
NonZeroI32
insideNaiveDate
(#1207)format::Numeric
andformat::Fixed
asnon_exhaustive
(#1430)Parsed
fixes to error values (#1439)overflowing_naive_local
inDateTime::checked_add*
(#1333)Parsed::set_*
(#1465)Documentation
Parsed
(#1439)Internal
internals
module (#1428, #1429, #1431, #1432, #1433, #1438)x86_64-unknown-illumos
instead of Solaris (#1437)cargo hack check
on Linux (#1442)parse_internal
(#1459)SerdeError
(#1458)NaiveDate::from_isoywd
a bit (#1464)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.34
Compare Source
Notable changes
Duration
type toTimeDelta
. This removes the confusion between chrono's type and the laterDuration
type in the standard library. It will remain available under the old name as a type alias for compatibility.Local
is rewritten. The new version avoids panics when the date is outside of the range supported by windows (the years 1601 to 30828), and gives more accurate results during DST transitions.Display
format ofTimeDelta
is modified to conform better to ISO 8601. Previously it converted all values greater than 24 hours to a value with days. This is not correct, as doing so changes the duration from an 'accurate' to a 'nominal' representation to use ISO 8601 terms.Fixes
TimeDelta::milliseconds
(#1385, thanks @danwilliams)DurationExceedsTimestamp
inDurationRound
(#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
Duration
toTimeDelta
, add type alias (#1406)TimeDelta
methods const (#1337)NaiveDate
,NaiveWeek
,NaiveTime
andNaiveDateTime
const where possible (#1337)DateTime
const where possible (#1400)Display
format ofTimeDelta
conform better to ISO 8601 (#1328)Documentation
timestamp_micros
's Example doc (#1338 via #1386, thanks @emikitas)TimeDelta
constructors (#1385, thanks @danwilliams)Internal
main
branch, work on 0.5 happens in the0.5.x
branch (#1390, #1402).impl Arbitrary for DateTime
and set up CI test (#1336)codecov/codecov-action
from 3 to 4 (#1404)-0000
offset (#1411)TOO_LONG
error out ofparse_internal
(#1419)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.33
Compare Source
This release fixes the broken docrs.rs build of chrono 0.4.32.
What's Changed
rkyv
feature implysize_32
(#1383)Duration::hours()
exception (#1384, thanks @danwilliams)v0.4.32
Compare Source
In this release we shipped part of the effort to reduce the number of methods that could unexpectedly panic, notably for the
DateTime
andDuration
types.Chrono internally stores the value of a
DateTime
in UTC, and transparently converts it to the local value as required. For example adding a second to aDateTime
needs to be done in UTC to get the correct result, but adding a day needs to be done in local time to be correct. What happens when the value is near the edge of the representable range, and the implicit conversions pushes it beyond the representable range? Many methods could panic on such inputs, including formatting the value forDebug
output.In chrono 0.4.32 the range of
NaiveDate
,NaiveDateTime
andDateTime
is made slightly smaller. This allows us to always do the implicit conversion, and in many cases return the expected result. Specifically the range is now from January 1, -262144 until December 31, 262143, one year less on both sides than before. We expect this may trip up tests if you hardcoded theMIN
andMAX
dates.Duration
had a similar issue. The range of this type was pretty arbitrary picked to match the range of ani64
in milliseconds. Negating ani64::MIN
pushes a value out of range, and in the same way negatingDuration::MIN
could push it out of our defined range and cause a panic. This turns out to be somewhat common and hidden behind many layers of abstraction. We adjusted the type to have a minimum value of-Duration::MAX
instead and prevent the panic case.Other highlights:
Duration
gained new fallible initialization methods.rkyv
.NaiveDateTime
are now const.DateTime
const in a future release.Complete list of changes:
Fixes
TimeZone::from_local_datetime
(#1071)DateTime
getters and setters (#1317, #1329)Additions
NaiveDateTime::checked_(add|sub)_offset
(#1313)DateTime::to_utc
(#1325)Default
forDuration
(#1327)Duration::subsec_nanos
(#1327)try_*
builders toDuration
(#1327)AddAssign
andSubAssign
forDuration
(#1327)NaiveDateTime
const where possible (#1286)clock
feature intoclock
andnow
(#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::MIN
by 1 millisecond) (#1334)Deprecations
format
functions (#1306)Documentation
doc_auto_cfg
(#1305, #1326)Add
/Sub
impls and useexpect
(#1316)TimeZone::datetime_from_str
(#1342, thanks @tmccombs)Datelike
impl forDateTime
(#1376, thanks @ElectrifyPro)Rkyv support
Archived*
types inrkyv
module (#1304)Archived*
types (#1271, thanks @Awpteamoose)Changes to unstable features
unstable-locales
imply thealloc
feature (#1307)format::{format_localized, format_item_localized}
(#1311)write_rfc2822_inner
, don't localize (#1322)Internal
DateTime::with_*
(#1309)*_DAYS_FROM_YEAR_0
calculation (#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)toml
job (#1371, thanks @gibbz00)Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.31
Compare 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_nanos
in 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_opt
andNaiveDateTime::timestamp_nanos_opt
(#1275)UNIX_EPOCH
constants (#1291)Fixes
This makes many methods a little more strict:
NaiveTime::from_hms_milli
NaiveTime::from_hms_milli_opt
NaiveTime::from_hms_micro
NaiveTime::from_hms_micro_opt
NaiveTime::from_hms_nano
NaiveTime::from_hms_nano_opt
NaiveTime::from_num_seconds_from_midnight
NaiveTime::from_num_seconds_from_midnight_opt
NaiveDate::and_hms_milli
NaiveDate::and_hms_milli_opt
NaiveDate::and_hms_micro
NaiveDate::and_hms_micro_opt
NaiveDate::and_hms_nano
NaiveDate::and_hms_nano_opt
NaiveDateTime::from_timestamp
NaiveDateTime::from_timestamp_opt
TimeZone::timestamp
TimeZone::timestamp_opt
NaiveDateTime::timestamp_nanos_opt
(#1294, thanks @crepererum)Documentation
Internal
__doctest
feature anddoc_comment
dependency (#1276)actions/checkout
from 3 to 4 (#1280)NaiveDate::add_days
for small values (#1214)pure-rust-locales
to 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.30
Compare Source
In this release, we have decided to swap out the
chrono::Duration
type (which has been a re-export of time 0.1Duration
type) with our own definition, which exposes a strict superset of thetime::Duration
API. This helps avoid warnings about the CVE-2020-26235 and RUSTSEC-2020-0071 advisories for downstream users and allows us to improve theDuration
API going forward.While this is technically a SemVer-breaking change, we expect the risk of downstream users experiencing actual incompatibility to be exceedingly limited (see our analysis 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_midnight
is a simple mapping (#1255)Relation between chrono and time 0.1
Rust first had a
time
module added tostd
in its 0.7 release. It later moved tolibextra
, and then to alibtime
library shipped alongside the standard library. In 2014 work on chrono started in order to provide a full-featured date and time library in Rust. Some improvements from chrono made it into the standard library; notably,chrono::Duration
was included asstd::time::Duration
(rust#15934) in 2014.In preparation of Rust 1.0 at the end of 2014
libtime
was moved out of the Rust distro and into thetime
crate to eventually be redesigned (rust#18832, rust#18858), like thenum
andrand
crates. Of course chrono kept its dependency on thistime
crate.time
started re-exportingstd::time::Duration
during this period. Later, the standard library was changed to have a more limited unsignedDuration
type (rust#24920, RFC 1040), while thetime
crate kept the full functionality withtime::Duration
.time::Duration
had been a part of chrono's public API.By 2016
time
0.1 lived under therust-lang-deprecated
organisation and was not actively maintained (time#136). chrono absorbed the platform functionality andDuration
type of thetime
crate in chrono#478 (the work started in chrono#286). In order to preserve compatibility with downstream crates depending ontime
andchrono
sharing aDuration
type, chrono kept depending on time 0.1. chrono offered the option to opt out of thetime
dependency by disabling theoldtime
feature (swapping it out for an effectively similar chrono type). In 2019, @jhpratt took over maintenance on thetime
crate and released what amounts to a new crate astime
0.2.Security advisories
In November of 2020 CVE-2020-26235 and RUSTSEC-2020-0071 were opened against the
time
crate. @quininer had found that calls tolocaltime_r
may be unsound (chrono#499). Eventually, almost a year later, this was also made into a security advisory against chrono as RUSTSEC-2020-0159, which had platform code similar totime
.On Unix-like systems a process is given a timezone id or description via the
TZ
environment variable. We need this timezone data to calculate the current local time from a value that is in UTC, such as the time from the system clock.time
0.1 and chrono used the POSIX functionlocaltime_r
to do the conversion to local time, which reads theTZ
variable.Rust assumes the environment to be writable and uses locks to access it from multiple threads. Some other programming languages and libraries use similar locking strategies, but these are typically not shared across languages. More importantly, POSIX declares modifying the environment in a multi-threaded process as unsafe, and
getenv
in libc can't be changed to take a lock because it returns a pointer to the data (see rust#27970 for more discussion).Since version 4.20 chrono no longer uses
localtime_r
, instead using Rust code to query the timezone (from theTZ
variable or viaiana-time-zone
as a fallback) and work with data from the system timezone database directly. The code for this was forked from the tz-rs crate by @x-hgg-x. As such, chrono now respects the Rust lock when reading theTZ
environment 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::Duration
type, there has been a long stream of issues from users inquiring about the time 0.1 dependency with the vulnerability. We investigated the potential breakage of removing the time 0.1 dependency in chrono#1095 using a crater-like experiment and determined that the potential for breaking (public) dependencies is very low. We reached out to those few crates that did still depend on compatibility with time 0.1.As such, for chrono 0.4.30 we have decided to swap out the time 0.1
Duration
implementation for a local one that will offer a strict superset of the existing API going forward. This will prevent most downstream users from being affected by the security vulnerability in time 0.1 while minimizing the ecosystem impact of semver-incompatible version churn.Thanks to all contributors on behalf of the chrono team, @djc and @pitdicker!
v0.4.29
Compare 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
FromStr
forWeekday
andMonth
(#1226, thanks @wfraser)Internal improvements
i686
andwasm32-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.28
Compare 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.27
Compare 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
NaiveDate
andNaiveTime
are made const,NaiveDateTime
and others will follow in a later release.The parser for the
%+
formatting specifier and theRFC3339
formatting 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_since
take argument withBorrow
(https://github.com/chronotope/chrono/pull/1119)PartialOrd
forMonth
(https://github.com/chronotope/chrono/pull/999, thanks @Munksgaard)Ord
andEq
for types which already derivePartialOrd
andPartialEq
(https://github.com/chronotope/chrono/pull/1128, thanks @totikom)FusedIterator
forNaiveDateDaysIterator
andNaiveDateWeeksIterator
(https://github.com/chronotope/chrono/pull/1134)NaiveDateDaysIterator
andNaiveDateWeeksIterator
public (https://github.com/chronotope/chrono/pull/1134)FromStr
forFixedOffset
(https://github.com/chronotope/chrono/pull/1157, thanks @mcronce)Tz::Offset: Display
requirement fromDateTime::to_rfc*
(https://github.com/chronotope/chrono/pull/1160)StrftimeItems
withunstable-locales
work without allocating (https://github.com/chronotope/chrono/pull/1152)NaiveDate::from_ymd_opt
const (https://github.com/chronotope/chrono/pull/1172, thanks @kamadorueda)Error
trait forParseWeekdayError
andParseMonthError
(https://github.com/chronotope/chrono/pull/539, thanks @mike-kfed)NaiveTime
const, update MSRV to 1.57 (https://github.com/chronotope/chrono/pull/1080)NaiveDate
const (https://github.com/chronotope/chrono/pull/1205)core::time::Duration
onDateTime
types (https://github.com/chronotope/chrono/pull/1229)Fixes
timestamp_nanos
panics on overflow in release builds (https://github.com/chronotope/chrono/pull/1123)offset_from_local_datetime
forwasm_bindgen
(https://github.com/chronotope/chrono/pull/1131)%s
to be a timestamp in UTC (https://github.com/chronotope/chrono/pull/1136)%#z
(https://github.com/chronotope/chrono/pull/1140, thanks @domodwyer)%c
and%r
(https://github.com/chronotope/chrono/pull/1165)unstable-locales
feature (https://github.com/chronotope/chrono/pull/1168)Offset
'sDebug
impl when serializingDateTime
(https://github.com/chronotope/chrono/pull/1035)NaiveTime::from_str
(https://github.com/chronotope/chrono/pull/1181)android-tzdata
if theclock
feature is not enabled (https://github.com/chronotope/chrono/pull/1220, thanks @AlexTMjugador)Documentation
NaiveTime
doc typo (https://github.com/chronotope/chrono/pull/1146, thanks @zachs18)Datelike::with_*
(https://github.com/chronotope/chrono/pull/1199)Utc::now
andLocal::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-bindgen
feature (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/Splittest_parse
chronotope/chrono#1170](https://togithuConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.