fix(deps): update rust crate time to v0.3.37 #27

Open
renovate-bot wants to merge 1 commit from renovate/time-0.x-lockfile into master
Member

This PR contains the following updates:

Package Type Update Change
time (source) dependencies patch 0.3.36 -> 0.3.37

Release Notes

time-rs/time (time)

v0.3.37

Compare Source

Added
  • Time::MAX, equivalent to time!(23:59:59.999999999)
  • [year repr:century] is now supported in format descriptions. When used in conjunction with
    [year repr:last_two], there is sufficient information to parse a date. Note that with the
    large-date feature enabled, there is an ambiguity when parsing the two back-to-back.
  • Parsing of strftime-style format descriptions, located at
    time::format_description::parse_strftime_borrowed and
    time::format_description::parse_strftime_owned
  • time::util::refresh_tz and time::util::refresh_tz_unchecked, which updates information
    obtained via the TZ environment variable. This is equivalent to the tzset syscall on Unix-like
    systems, with and without built-in soundness checks, respectively.
  • Month::length and util::days_in_month, replacing util::days_in_year_month.
  • Expressions are permitted in time::serde::format_description! rather than only paths. This also
    drastically improves diagnostics when an invalid value is provided.
Changed
  • Obtaining the system UTC offset on Unix-like systems should now succeed when multi-threaded.
    However, if the TZ environment variable is altered, the program will not be aware of this until
    time::util::refresh_tz or time::util::refresh_tz_unchecked is called. refresh_tz has the
    same soundness requirements as obtaining the system UTC offset previously did, with the
    requirements still being automatically enforced. refresh_tz_unchecked does not enforce these
    requirements at the expense of being unsafe. Most programs should not need to call either
    function.

    Due to this change, the time::util::local_offset module has been deprecated in its entirety. The
    get_soundness and set_soundness functions are now no-ops.

    Note that while calls should succeed, success is not guaranteed in any situation. Downstream
    users should always be prepared to handle the error case.

Fixed
  • Floating point values are truncated, not rounded, when formatting.
  • RFC3339 allows arbitrary separators between the date and time components.
  • Serialization of negative Durations less than one second is now correct. It previously omitted
    the negative sign.
  • From<js_sys::Date> for OffsetDateTime now ensures sub-millisecond values are not erroneously
    returned.

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

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [time](https://time-rs.github.io) ([source](https://github.com/time-rs/time)) | dependencies | patch | `0.3.36` -> `0.3.37` | --- ### Release Notes <details> <summary>time-rs/time (time)</summary> ### [`v0.3.37`](https://github.com/time-rs/time/blob/HEAD/CHANGELOG.md#0337-2024-12-03) [Compare Source](https://github.com/time-rs/time/compare/v0.3.36...v0.3.37) ##### Added - `Time::MAX`, equivalent to `time!(23:59:59.999999999)` - `[year repr:century]` is now supported in format descriptions. When used in conjunction with `[year repr:last_two]`, there is sufficient information to parse a date. Note that with the `large-date` feature enabled, there is an ambiguity when parsing the two back-to-back. - Parsing of `strftime`-style format descriptions, located at `time::format_description::parse_strftime_borrowed` and `time::format_description::parse_strftime_owned` - `time::util::refresh_tz` and `time::util::refresh_tz_unchecked`, which updates information obtained via the `TZ` environment variable. This is equivalent to the `tzset` syscall on Unix-like systems, with and without built-in soundness checks, respectively. - `Month::length` and `util::days_in_month`, replacing `util::days_in_year_month`. - Expressions are permitted in `time::serde::format_description!` rather than only paths. This also drastically improves diagnostics when an invalid value is provided. ##### Changed - Obtaining the system UTC offset on Unix-like systems should now succeed when multi-threaded. However, if the `TZ` environment variable is altered, the program will not be aware of this until `time::util::refresh_tz` or `time::util::refresh_tz_unchecked` is called. `refresh_tz` has the same soundness requirements as obtaining the system UTC offset previously did, with the requirements still being automatically enforced. `refresh_tz_unchecked` does not enforce these requirements at the expense of being `unsafe`. Most programs should not need to call either function. Due to this change, the `time::util::local_offset` module has been deprecated in its entirety. The `get_soundness` and `set_soundness` functions are now no-ops. Note that while calls *should* succeed, success is not guaranteed in any situation. Downstream users should always be prepared to handle the error case. ##### Fixed - Floating point values are truncated, not rounded, when formatting. - RFC3339 allows arbitrary separators between the date and time components. - Serialization of negative `Duration`s less than one second is now correct. It previously omitted the negative sign. - `From<js_sys::Date> for OffsetDateTime` now ensures sub-millisecond values are not erroneously returned. </details> --- ### 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. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiIzOS44Mi4yIiwidXBkYXRlZEluVmVyIjoiMzkuODIuMiIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6WyJyZW5vdmF0ZS1ib3QiXX0=-->
renovate-bot added the
renovate-bot
label 2024-12-23 18:13:51 +05:30
renovate-bot added 1 commit 2024-12-23 18:13:51 +05:30
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/time-0.x-lockfile:renovate/time-0.x-lockfile
git checkout renovate/time-0.x-lockfile

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout master
git merge --no-ff renovate/time-0.x-lockfile
git checkout renovate/time-0.x-lockfile
git rebase master
git checkout master
git merge --ff-only renovate/time-0.x-lockfile
git checkout renovate/time-0.x-lockfile
git rebase master
git checkout master
git merge --no-ff renovate/time-0.x-lockfile
git checkout master
git merge --squash renovate/time-0.x-lockfile
git checkout master
git merge --ff-only renovate/time-0.x-lockfile
git checkout master
git merge renovate/time-0.x-lockfile
git push origin master
Sign in to join this conversation.
No description provided.