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

chore(deps): bump chrono from 0.4.34 to 0.4.35 #2

Merged
merged 3 commits into from
Mar 9, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 8, 2024

Bumps chrono from 0.4.34 to 0.4.35.

Release notes

Sourced from chrono's releases.

v0.4.35

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

  • Rustfmt doctests (#1452)
  • Improve docs for crate features (#1455, thanks @​edmorley)
  • Add more documentation and examples to Parsed (#1439)

Internal

  • Refactor internals module (#1428, #1429, #1431, #1432, #1433, #1438)
  • CI: test cross-compiling to x86_64-unknown-illumos instead of Solaris (#1437)
  • CI: lint Windows target, fix clippy warning (#1441)
  • CI: only run cargo hack check on Linux (#1442)
  • Update windows-bindgen to 0.54 (#1462, #1483)
  • Simplify error value of parse_internal (#1459)
  • Simplify SerdeError (#1458)
  • Simplify NaiveDate::from_isoywd a bit (#1464)

... (truncated)

Commits
  • 9fdb596 Prepare 0.4.35
  • 9e667b6 Deprecate panicking TimeDelta constructors
  • 2c1b0be Tests: replace TimeDelta::milliseconds with try_milliseconds
  • 2bf3302 Tests: replace TimeDelta::seconds with try_seconds
  • f93508f Tests: replace TimeDelta::minutes with try_minutes
  • 9fc931a Tests: replace TimeDelta::hours with try_hours
  • 9f23c08 Tests: replace TimeDelta::days with try_days
  • e8f9b5e Tests: replace TimeDelta::weeks with try_weeks
  • 51a1aa2 Tests: use Days type when it is more appropriate than TimeDelta
  • 4251bd1 Replace TimeDelta::seconds with try_seconds
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [chrono](https://github.com/chronotope/chrono) from 0.4.34 to 0.4.35.
- [Release notes](https://github.com/chronotope/chrono/releases)
- [Changelog](https://github.com/chronotope/chrono/blob/main/CHANGELOG.md)
- [Commits](chronotope/chrono@v0.4.34...v0.4.35)

---
updated-dependencies:
- dependency-name: chrono
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 8, 2024
@m1 m1 merged commit b82ab35 into master Mar 9, 2024
14 checks passed
@m1 m1 deleted the dependabot/cargo/chrono-0.4.35 branch March 9, 2024 20:06
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