-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update rust crate chrono to 0.4.35 #318
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
fix(deps): update rust crate chrono to 0.4.25
fix(deps): update rust crate chrono to 0.4.26
May 30, 2023
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
2 times, most recently
from
June 5, 2023 03:26
b5b6d15
to
52d9768
Compare
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
2 times, most recently
from
June 12, 2023 04:09
303615d
to
95ccc9a
Compare
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
2 times, most recently
from
June 19, 2023 04:14
73f7045
to
7ebe5e5
Compare
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
3 times, most recently
from
June 26, 2023 02:44
98a7c9e
to
6e99443
Compare
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
10 times, most recently
from
July 10, 2023 03:18
b9b863c
to
decedcb
Compare
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
8 times, most recently
from
July 17, 2023 04:00
0dc2df9
to
c99b321
Compare
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
2 times, most recently
from
July 20, 2023 05:07
123e5f6
to
fb2b098
Compare
renovate
bot
changed the title
fix(deps): update rust crate chrono to 0.4.26
fix(deps): update rust crate chrono to 0.4.27
Aug 29, 2023
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
from
August 29, 2023 14:33
d9d8d62
to
d324ec6
Compare
renovate
bot
changed the title
fix(deps): update rust crate chrono to 0.4.27
fix(deps): update rust crate chrono to 0.4.28
Aug 30, 2023
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
from
August 30, 2023 21:54
d324ec6
to
9331eb4
Compare
renovate
bot
changed the title
fix(deps): update rust crate chrono to 0.4.28
fix(deps): update rust crate chrono to 0.4.29
Sep 5, 2023
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
3 times, most recently
from
September 6, 2023 12:12
6498f3f
to
152c4e7
Compare
renovate
bot
changed the title
fix(deps): update rust crate chrono to 0.4.29
fix(deps): update rust crate chrono to 0.4.30
Sep 7, 2023
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
5 times, most recently
from
September 14, 2023 03:45
d2ee839
to
8eaaaf6
Compare
renovate
bot
changed the title
fix(deps): update rust crate chrono to 0.4.30
fix(deps): update rust crate chrono to 0.4.31
Sep 15, 2023
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
2 times, most recently
from
September 18, 2023 04:46
dff7059
to
0de14df
Compare
renovate
bot
changed the title
fix(deps): update rust crate chrono to 0.4.31
fix(deps): update rust crate chrono to 0.4.32
Jan 23, 2024
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
from
January 23, 2024 01:46
0de14df
to
4bcfed7
Compare
renovate
bot
changed the title
fix(deps): update rust crate chrono to 0.4.32
fix(deps): update rust crate chrono to 0.4.33
Jan 25, 2024
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
from
January 25, 2024 15:06
4bcfed7
to
7484072
Compare
renovate
bot
changed the title
fix(deps): update rust crate chrono to 0.4.33
fix(deps): update rust crate chrono to 0.4.34
Feb 11, 2024
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
from
February 11, 2024 07:10
7484072
to
4c6fb7c
Compare
renovate
bot
changed the title
fix(deps): update rust crate chrono to 0.4.34
fix(deps): update rust crate chrono to 0.4.35
Mar 6, 2024
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
from
March 6, 2024 14:26
4c6fb7c
to
0ed4af6
Compare
renovate
bot
force-pushed
the
renovate/chrono-0.x
branch
from
March 21, 2024 21:00
0ed4af6
to
8cbd588
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
0.4.24
->0.4.35
Release Notes
chronotope/chrono (chrono)
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
: 0.4.34Compare 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
: 0.4.33Compare 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!
Configuration
📅 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.