Skip to content

Commit

Permalink
v0.3.37 release
Browse files Browse the repository at this point in the history
  • Loading branch information
jhpratt committed Dec 3, 2024
1 parent 0943997 commit d4e39b3
Show file tree
Hide file tree
Showing 5 changed files with 46 additions and 6 deletions.
42 changes: 41 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,49 @@ The format is based on [Keep a Changelog]. This project adheres to [Semantic Ver

---

## 0.3.37 [2024-12-03]

### 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.

## 0.3.36 [2024-04-10]

### # Fixed
### Fixed

- `FormatItem` can be used as part of an import path. See [#675] for details.

Expand Down
4 changes: 2 additions & 2 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ resolver = "2"

[workspace.dependencies]
time-core = { path = "time-core", version = "=0.1.2" }
time-macros = { path = "time-macros", version = "=0.2.18" }
time-macros = { path = "time-macros", version = "=0.2.19" }

criterion = { version = "0.5.1", default-features = false }
deranged = { version = "0.3.9", default-features = false, features = [
Expand Down
2 changes: 1 addition & 1 deletion time-macros/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "time-macros"
version = "0.2.18"
version = "0.2.19"
authors = ["Jacob Pratt <[email protected]>", "Time contributors"]
edition = "2021"
rust-version = "1.67.1"
Expand Down
2 changes: 1 addition & 1 deletion time/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "time"
version = "0.3.36"
version = "0.3.37"
authors = ["Jacob Pratt <[email protected]>", "Time contributors"]
edition = "2021"
rust-version = "1.67.1"
Expand Down

0 comments on commit d4e39b3

Please sign in to comment.