pierre/BasicOIDC
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Update Rust crate chrono to 0.4.35 #247

Closed
pierre wants to merge 1 commits from renovate/chrono-0.x into master
pull from: renovate/chrono-0.x
merge into: pierre:master
Conversation 2 Commits 1 Files Changed 2 +3 -3
pierre commented 2024-03-07 00:11:13 +00:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
chrono dependencies patch 0.4.34 -> 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!

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.

🔕 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 Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [chrono](https://github.com/chronotope/chrono) | dependencies | patch | `0.4.34` -> `0.4.35` | --- ### Release Notes <details> <summary>chronotope/chrono (chrono)</summary> ### [`v0.4.35`](https://github.com/chronotope/chrono/releases/tag/v0.4.35) [Compare Source](https://github.com/chronotope/chrono/compare/v0.4.34...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}` ([#&#8203;1234](https://github.com/chronotope/chrono/issues/1234)) - Add getters to `Parsed` ([#&#8203;1465](https://github.com/chronotope/chrono/issues/1465)) ### Deprecations - Deprecate timestamp methods on `NaiveDateTime` ([#&#8203;1473](https://github.com/chronotope/chrono/issues/1473)) - Deprecate panicking constructors of `TimeDelta` ([#&#8203;1450](https://github.com/chronotope/chrono/issues/1450)) ### Changes/fixes - Use `NonZeroI32` inside `NaiveDate` ([#&#8203;1207](https://github.com/chronotope/chrono/issues/1207)) - Mark `format::Numeric` and `format::Fixed` as `non_exhaustive` ([#&#8203;1430](https://github.com/chronotope/chrono/issues/1430)) - `Parsed` fixes to error values ([#&#8203;1439](https://github.com/chronotope/chrono/issues/1439)) - Use `overflowing_naive_local` in `DateTime::checked_add*` ([#&#8203;1333](https://github.com/chronotope/chrono/issues/1333)) - Do complete range checks in `Parsed::set_*` ([#&#8203;1465](https://github.com/chronotope/chrono/issues/1465)) ### Documentation - Rustfmt doctests ([#&#8203;1452](https://github.com/chronotope/chrono/issues/1452)) - Improve docs for crate features ([#&#8203;1455](https://github.com/chronotope/chrono/issues/1455), thanks [@&#8203;edmorley](https://github.com/edmorley)) - Add more documentation and examples to `Parsed` ([#&#8203;1439](https://github.com/chronotope/chrono/issues/1439)) ### Internal - Refactor `internals` module ([#&#8203;1428](https://github.com/chronotope/chrono/issues/1428), [#&#8203;1429](https://github.com/chronotope/chrono/issues/1429), [#&#8203;1431](https://github.com/chronotope/chrono/issues/1431), [#&#8203;1432](https://github.com/chronotope/chrono/issues/1432), [#&#8203;1433](https://github.com/chronotope/chrono/issues/1433), [#&#8203;1438](https://github.com/chronotope/chrono/issues/1438)) - CI: test cross-compiling to `x86_64-unknown-illumos` instead of Solaris ([#&#8203;1437](https://github.com/chronotope/chrono/issues/1437)) - CI: lint Windows target, fix clippy warning ([#&#8203;1441](https://github.com/chronotope/chrono/issues/1441)) - CI: only run `cargo hack check` on Linux ([#&#8203;1442](https://github.com/chronotope/chrono/issues/1442)) - Update windows-bindgen to 0.54 ([#&#8203;1462](https://github.com/chronotope/chrono/issues/1462), [#&#8203;1483](https://github.com/chronotope/chrono/issues/1483)) - Simplify error value of `parse_internal` ([#&#8203;1459](https://github.com/chronotope/chrono/issues/1459)) - Simplify `SerdeError` ([#&#8203;1458](https://github.com/chronotope/chrono/issues/1458)) - Simplify `NaiveDate::from_isoywd` a bit ([#&#8203;1464](https://github.com/chronotope/chrono/issues/1464)) Thanks to all contributors on behalf of the chrono team, [@&#8203;djc](https://github.com/djc) and [@&#8203;pitdicker](https://github.com/pitdicker)! </details> --- ### 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. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yMzAuMCIsInVwZGF0ZWRJblZlciI6IjM3LjIzMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIn0=-->
pierre added 1 commit 2024-03-07 00:11:15 +00:00
Update Rust crate chrono to 0.4.35
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone/pr Build is failing
Details
aeec88e479
pierre scheduled this pull request to auto merge when all checks succeed 2024-03-07 00:11:16 +00:00
pierre commented 2024-03-08 00:10:28 +00:00
Author
Owner
Copy Link

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

### Edited/Blocked Notification Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ **Warning**: custom changes will be lost.
pierre commented 2024-03-15 15:41:23 +00:00
Author
Owner
Copy Link

Fixed in 06766a2af4

Fixed in 06766a2af42ad6ac179f1402e2a159fb831f9fff
pierre closed this pull request 2024-03-15 15:41:23 +00:00
pierre deleted branch renovate/chrono-0.x 2024-03-15 15:41:26 +00:00
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone/pr Build is failing
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate pierre
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: pierre/BasicOIDC#247
No description provided.
Delete Branch "renovate/chrono-0.x"

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?