Update Rust crate time to v0.3.37 #147

Renovate · 2024-12-03T02:53:21-05:00

Renovate commented

2024-12-03 02:53:21 -05:00

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.

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: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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. ##### 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**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, 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](https://github.com/renovatebot/renovate).

Renovate added 1 commit 2024-12-03 02:53:22 -05:00

Update Rust crate time to v0.3.37 892b0fb55b

PR created by Renovate Bot.

Renovate merged commit 697778dce2 into master

2024-12-03 02:53:35 -05:00

Renovate referenced this issue from a commit

2024-12-03 02:53:37 -05:00

Update Rust crate time to v0.3.37 (#147)

Sign in to join this conversation.

No reviewers

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: toast/Rustbot#147