Skip to content
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
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 29, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
chrono dependencies patch 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. The NaiveDateTime 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 the DateTime<Utc> type, or from the TimeZone trait.

    Converting from NaiveDateTime to DateTime<Utc> is simple with .and_utc(), and in the other direction with .naive_utc().

  • The panicking constructors of TimeDelta (the new name of the Duration 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 now Option<NaiveDate>, Option<NaiveDateTime> and Option<DateTime<Tz>> are the same size as their base types.

  • format::Numeric and format::Fixed are marked as non_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

  • Add DateTime::{from_timestamp_micros, from_timestamp_nanos} (#​1234)
  • Add getters to Parsed (#​1465)

Deprecations

  • Deprecate timestamp methods on NaiveDateTime (#​1473)
  • Deprecate panicking constructors of TimeDelta (#​1450)

Changes/fixes

  • Use NonZeroI32 inside NaiveDate (#​1207)
  • Mark format::Numeric and format::Fixed as non_exhaustive (#​1430)
  • Parsed fixes to error values (#​1439)
  • Use overflowing_naive_local in DateTime::checked_add* (#​1333)
  • Do complete range checks in Parsed::set_* (#​1465)

Documentation

Internal

Thanks to all contributors on behalf of the chrono team, @​djc and @​pitdicker!

v0.4.34: 0.4.34

Compare Source

Notable changes

  • In chrono 0.4.34 we finished the work to make all methods const where doing so is supported by rust 1.61.
  • We renamed the Duration type to TimeDelta. This removes the confusion between chrono's type and the later Duration type in the standard library. It will remain available under the old name as a type alias for compatibility.
  • The Windows implementation of 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.
  • The Display format of TimeDelta 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

Additions

Changes

  • Rename Duration to TimeDelta, add type alias (#​1406)
  • Make TimeDelta methods const (#​1337)
  • Make remaining methods of NaiveDate, NaiveWeek, NaiveTime and NaiveDateTime const where possible (#​1337)
  • Make methods on DateTime const where possible (#​1400)
  • Make Display format of TimeDelta conform better to ISO 8601 (#​1328)

Documentation

Internal

  • Switch branch names: 0.4.x releases are the main branch, work on 0.5 happens in the 0.5.x branch (#​1390, #​1402).
  • Don't use deprecated method in impl Arbitrary for DateTime and set up CI test (#​1336)
  • Remove workaround for Rust < 1.61 (#​1393)
  • Bump codecov/codecov-action from 3 to 4 (#​1404)
  • Remove partial support for handling -0000 offset (#​1411)
  • Move TOO_LONG error out of parse_internal (#​1419)

Thanks to all contributors on behalf of the chrono team, @​djc and @​pitdicker!

v0.4.33: 0.4.33

Compare Source

This release fixes the broken docrs.rs build of chrono 0.4.32.

What's Changed

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 and Duration 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 a DateTime 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 for Debug output.

In chrono 0.4.32 the range of NaiveDate, NaiveDateTime and DateTime 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 the MIN and MAX dates.

Duration had a similar issue. The range of this type was pretty arbitrary picked to match the range of an i64 in milliseconds. Negating an i64::MIN pushes a value out of range, and in the same way negating Duration::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.
  • Better support for rkyv.
  • Most methods on NaiveDateTime are now const.
  • We had to bump our MSRV to 1.61 to keep building with our dependencies. This will also allow us to make more methods on DateTime const in a future release.

Complete list of changes:

Fixes

  • Fix panic in TimeZone::from_local_datetime (#​1071)
  • Fix out of range panics in DateTime getters and setters (#​1317, #​1329)

Additions

Changes

  • Fix panic in Duration::MIN.abs() (adjust Duration::MIN by 1 millisecond) (#​1334)
  • Bump MSRV to 1.61 (#​1347)
  • Update windows-targets requirement from 0.48 to 0.52 (#​1360)
  • Update windows-bindgen to 0.52 (#​1379)

Deprecations

  • Deprecate standalone format functions (#​1306)

Documentation

Rkyv support

Changes to unstable features

  • Don't let unstable-locales imply the alloc feature (#​1307)
  • Remove format::{format_localized, format_item_localized} (#​1311)
  • Inline write_rfc2822_inner, don't localize (#​1322)

Internal

  • Add benchmark for DateTime::with_* (#​1309)
  • Fix *_DAYS_FROM_YEAR_0 calculation (#​1312)
  • Add NaiveTime::overflowing_(add|sub)_offset (#​1310)
  • Rewrite DateTime::overflowing_(add|sub)_offset (#​1069)
  • Tests calling date command set env LC_ALL (#​1315, thanks @​jtmoon79)
  • Update deny.toml (#​1320)
  • Bump actions/setup-node from 3 to 4 (#​1346)
  • test.yml remove errant with: node-version (#​1352, thanks @​jtmoon79)
  • CI Linting: Fix missing sources checkout in toml job (#​1371, thanks @​gibbz00)
  • Silence clippy lint for test code with Rust 1.74.0 (#​1362)

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate 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 renovate bot force-pushed the renovate/chrono-0.x branch 2 times, most recently from b5b6d15 to 52d9768 Compare June 5, 2023 03:26
@renovate renovate bot force-pushed the renovate/chrono-0.x branch 2 times, most recently from 303615d to 95ccc9a Compare June 12, 2023 04:09
@renovate renovate bot force-pushed the renovate/chrono-0.x branch 2 times, most recently from 73f7045 to 7ebe5e5 Compare June 19, 2023 04:14
@renovate renovate bot force-pushed the renovate/chrono-0.x branch 3 times, most recently from 98a7c9e to 6e99443 Compare June 26, 2023 02:44
@renovate renovate bot force-pushed the renovate/chrono-0.x branch 10 times, most recently from b9b863c to decedcb Compare July 10, 2023 03:18
@renovate renovate bot force-pushed the renovate/chrono-0.x branch 8 times, most recently from 0dc2df9 to c99b321 Compare July 17, 2023 04:00
@renovate renovate bot force-pushed the renovate/chrono-0.x branch 2 times, most recently from 123e5f6 to fb2b098 Compare July 20, 2023 05:07
@renovate 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 renovate bot force-pushed the renovate/chrono-0.x branch from d9d8d62 to d324ec6 Compare August 29, 2023 14:33
@renovate 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 renovate bot force-pushed the renovate/chrono-0.x branch from d324ec6 to 9331eb4 Compare August 30, 2023 21:54
@renovate 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 renovate bot force-pushed the renovate/chrono-0.x branch 3 times, most recently from 6498f3f to 152c4e7 Compare September 6, 2023 12:12
@renovate 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 renovate bot force-pushed the renovate/chrono-0.x branch 5 times, most recently from d2ee839 to 8eaaaf6 Compare September 14, 2023 03:45
@renovate 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 renovate bot force-pushed the renovate/chrono-0.x branch 2 times, most recently from dff7059 to 0de14df Compare September 18, 2023 04:46
@renovate 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 renovate bot force-pushed the renovate/chrono-0.x branch from 0de14df to 4bcfed7 Compare January 23, 2024 01:46
@renovate 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 renovate bot force-pushed the renovate/chrono-0.x branch from 4bcfed7 to 7484072 Compare January 25, 2024 15:06
@renovate 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 renovate bot force-pushed the renovate/chrono-0.x branch from 7484072 to 4c6fb7c Compare February 11, 2024 07:10
@renovate 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 renovate bot force-pushed the renovate/chrono-0.x branch from 4c6fb7c to 0ed4af6 Compare March 6, 2024 14:26
@renovate renovate bot force-pushed the renovate/chrono-0.x branch from 0ed4af6 to 8cbd588 Compare March 21, 2024 21:00
@Elsie19 Elsie19 closed this Mar 21, 2024
@Elsie19 Elsie19 deleted the renovate/chrono-0.x branch March 21, 2024 21:09
Copy link
Contributor Author

renovate bot commented Mar 21, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (0.4.35). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant