[PR #1045] [CLOSED] Bump time from 0.1.42 to 0.2.9 #1917

New issue

Closed

opened 2026-03-16 03:42:51 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 03:42:51 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/1045
Author: @dependabot-preview[bot]
Created: 3/18/2020
Status: ❌ Closed

Base: master ← Head: dependabot/cargo/time-0.2.9

📝 Commits (2)

525e8a7 Bump time from 0.1.42 to 0.2.9
1c38aa9 Merge branch 'master' into dependabot/cargo/time-0.2.9

📊 Changes

2 files changed (+164 additions, -2 deletions)

View changed files

📝 Cargo.lock (+163 -1)
📝 crates/server/Cargo.toml (+1 -1)

📄 Description

Bumps time from 0.1.42 to 0.2.9.

Release notes

Sourced from time's releases.

v0.2.9

No release notes provided.

v0.2.8

No release notes provided.

v0.2.7

All changes are now being reported in the repository's changelog.

v0.2.6

Bug fixes

v0.2.5 introduces a major inconsistency, not just in its behavior for PrimitiveDateTime::using_offset, but also changes its signature, rendering it incapable of being used in const contexts.

Both the behavior and the function signature have been fixed, while still fixing the underlying issue. PrimitiveDateTime::using_offset mentions in the docs that the PrimitiveDateTime is assumed to be UTC, and is converted to the provided offset. This was the previous behavior.

The following functionality had bugs that were fixed (from v0.2.4):

OffsetDateTime::timestamp

OffsetDateTime::parse

Equality, comparison for OffsetDateTime — Subsecond values were not checked previously. They also relied on the faulty timestamp implementation.

Hashing of OffsetDateTime — Same as equality and comparison. Additionally, hashes would collide with PrimitiveDateTime if the underlying UTC was the same.

Subtraction of two OffsetDateTimes previously disregarded the subsecond values.

All of these changes are now checked in CI, so regressions will be caught.

v0.2.5

Bug fixes

PrimitiveDateTime::using_offset was poorly defined, leading to an ambiguity that cause some methods to treat the existing datetime as UTC, while others treated it as the time in the provided offset. This release ensures that the behavior is what I intended — the datetime is assumed to be in the provided offset.

NB: This release has been yanked from crates.io due to major back-compatibility issues. These have been fixed in 0.2.6.

v0.2.4 is identical to v0.2.3 with the exception of the breaking change, which has been reverted. v0.2.4 is backwards-compatible with v0.2.2.

v0.2.3 has been yanked from crates.io. The breaking change (with regard to feature flags) should not have been made. By yanking this version, any existing code will continue to work, while new code will not have potential backwards-incompatible behavior. The change was reverted in v0.2.4.

Additions

time!, date!, offset! macros

Top-level parse function, allowing for type inference.

time::Result<T> alias to time::Result<T, time::Error>

Deprecated

Panicking APIs have been deprecated in favor of the new macros.

Changes

Minimum supported Rust version is now 1.34, changed from 1.40. This permits a number of crates to upgrade without breaking MSRV.
... (truncated)

Changelog

Sourced from time's changelog.

0.2.9 [2020-03-13]

Fixed

cfg-if now has a mandatory minimum of 0.1.10, rather than just 0.1. This is because compilation fails when using 0.1.9.

0.2.8 [2020-03-12]

Added

cargo_web support has been added for getting a local offset. A general catch-all defaulting to UTC has also been added.

Error::source has been implemented for the wrapper time::Error.

UtcOffset::try_local_offset, UtcOffset::try_current_local_offset, OffsetDateTime::try_now_local() provide fallible alternatives when the default of UTC is not desired. To facilitate this change, IndeterminateOffsetError has been added.

Support for parsing and formatting subsecond nanoseconds.

Changed

#[non_exhaustive] is simulated on compilers prior to 1.40.0.

0.2.7 [2020-02-22]

Added

Display has been implemented for Date, OffsetDateTime, PrimitiveDateTime, Time, UtcOffset, and Weekday.

Hash is now derived for Duration.

SystemTime can be converted to and from OffsetDateTime. The following trait implementations have been made for interoperability:

impl Sub<SystemTime> for OffsetDateTime

impl Sub<OffsetDateTime> for SystemTime

impl PartialEq<SystemTime> for OffsetDateTime

impl PartialEq<OffsetDateTime> for SystemTime

impl PartialOrd<SystemTime> for OffsetDateTime

impl PartialOrd<OffsetDateTime> for SystemTime

impl From<SystemTime> for OffsetDateTime

impl From<OffsetDateTime> for SystemTime

All structs now impl Duration<T> for Standard, allowing usage with the rand crate. This is gated behind the rand feature flag.

Documentation can now be built on stable. Some annotations will be missing if you do this.

NumericalDuration has been implemented for f32 and f64. NumericalStdDuration and NumericalStdDurationShort have been implemented for f64 only.

UtcOffset::local_offset_at(OffsetDateTime), which will obtain the system's

... (truncated)

Commits

See full diff in compare view

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 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)
@dependabot use these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
@dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

Update frequency (including time of day and day of week)
Pull request limits (per update run and/or open at any time)
Automerge options (never/patch/minor, and dev/runtime dependencies)
Out-of-range updates (receive only lockfile updates, if desired)
Security updates (receive only security updates, if desired)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hickory-dns/hickory-dns/pull/1045 **Author:** [@dependabot-preview[bot]](https://github.com/apps/dependabot-preview) **Created:** 3/18/2020 **Status:** ❌ Closed **Base:** `master` ← **Head:** `dependabot/cargo/time-0.2.9` --- ### 📝 Commits (2) - [`525e8a7`](https://github.com/hickory-dns/hickory-dns/commit/525e8a750f05b4917de14d7b255d4f3fc38be0b9) Bump time from 0.1.42 to 0.2.9 - [`1c38aa9`](https://github.com/hickory-dns/hickory-dns/commit/1c38aa9f4cac8e9edc2a4446e20b2570a5a9df6f) Merge branch 'master' into dependabot/cargo/time-0.2.9 ### 📊 Changes **2 files changed** (+164 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `Cargo.lock` (+163 -1) 📝 `crates/server/Cargo.toml` (+1 -1) </details> ### 📄 Description Bumps [time](https://github.com/time-rs/time) from 0.1.42 to 0.2.9. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/time-rs/time/releases">time's releases</a>.</em></p> <blockquote> <h2>v0.2.9</h2> <p>No release notes provided.</p> <h2>v0.2.8</h2> <p>No release notes provided.</p> <h2>v0.2.7</h2> <p>All changes are now being reported in the repository's changelog.</p> <h2>v0.2.6</h2> <h3>Bug fixes</h3> <p>v0.2.5 introduces a major inconsistency, not just in its behavior for <code>PrimitiveDateTime::using_offset</code>, but also changes its signature, rendering it incapable of being used in <code>const</code> contexts.</p> <p>Both the behavior and the function signature have been fixed, while still fixing the underlying issue. <code>PrimitiveDateTime::using_offset</code> mentions in the docs that the <code>PrimitiveDateTime</code> is assumed to be UTC, and is converted to the provided offset. This was the previous behavior.</p> <p>The following functionality had bugs that were fixed (from v0.2.4):</p> <ul> <li><code>OffsetDateTime::timestamp</code></li> <li><code>OffsetDateTime::parse</code></li> <li>Equality, comparison for <code>OffsetDateTime</code> — Subsecond values were not checked previously. They also relied on the faulty timestamp implementation.</li> <li>Hashing of <code>OffsetDateTime</code> — Same as equality and comparison. Additionally, hashes would collide with <code>PrimitiveDateTime</code> if the underlying UTC was the same.</li> <li>Subtraction of two <code>OffsetDateTime</code>s previously disregarded the subsecond values.</li> </ul> <p>All of these changes are now checked in CI, so regressions will be caught.</p> <h2>v0.2.5</h2> <h3>Bug fixes</h3> <p><code>PrimitiveDateTime::using_offset</code> was poorly defined, leading to an ambiguity that cause some methods to treat the existing datetime as UTC, while others treated it as the time in the provided offset. This release ensures that the behavior is what I intended — the datetime is assumed to be in the provided offset.</p> <p>NB: This release has been yanked from crates.io due to major back-compatibility issues. These have been fixed in 0.2.6.</p> <p>v0.2.4 is identical to v0.2.3 with the exception of the breaking change, which has been reverted. v0.2.4 is backwards-compatible with v0.2.2.</p> <p>v0.2.3 has been yanked from crates.io. The breaking change (with regard to feature flags) should not have been made. By yanking this version, any existing code will continue to work, while new code will not have potential backwards-incompatible behavior. The change was reverted in v0.2.4.</p> <h3>Additions</h3> <ul> <li><code>time!</code>, <code>date!</code>, <code>offset!</code> macros</li> <li>Top-level <code>parse</code> function, allowing for type inference.</li> <li><code>time::Result<T></code> alias to <code>time::Result<T, time::Error></code></li> </ul> <h3>Deprecated</h3> <p>Panicking APIs have been deprecated in favor of the new macros.</p> <h3>Changes</h3> <p>Minimum supported Rust version is now 1.34, changed from 1.40. This permits a number of crates to upgrade without breaking MSRV.</p> </tr></table> ... (truncated) </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/time-rs/time/blob/master/CHANGELOG.md">time's changelog</a>.</em></p> <blockquote> <h2>0.2.9 [2020-03-13]</h2> <h3>Fixed</h3> <p><code>cfg-if</code> now has a mandatory minimum of 0.1.10, rather than just 0.1. This is because compilation fails when using 0.1.9.</p> <h2>0.2.8 [2020-03-12]</h2> <h3>Added</h3> <ul> <li><code>cargo_web</code> support has been added for getting a local offset. A general catch-all defaulting to UTC has also been added.</li> <li><code>Error::source</code> has been implemented for the wrapper <code>time::Error</code>.</li> <li><code>UtcOffset::try_local_offset</code>, <code>UtcOffset::try_current_local_offset</code>, <code>OffsetDateTime::try_now_local()</code> provide fallible alternatives when the default of UTC is not desired. To facilitate this change, <code>IndeterminateOffsetError</code> has been added.</li> <li>Support for parsing and formatting subsecond nanoseconds.</li> </ul> <h3>Changed</h3> <ul> <li><code>#[non_exhaustive]</code> is simulated on compilers prior to 1.40.0.</li> </ul> <h2>0.2.7 [2020-02-22]</h2> <h3>Added</h3> <ul> <li> <p><code>Display</code> has been implemented for <code>Date</code>, <code>OffsetDateTime</code>, <code>PrimitiveDateTime</code>, <code>Time</code>, <code>UtcOffset</code>, and <code>Weekday</code>.</p> </li> <li> <p><code>Hash</code> is now derived for <code>Duration</code>.</p> </li> <li> <p><code>SystemTime</code> can be converted to and from <code>OffsetDateTime</code>. The following trait implementations have been made for interoperability:</p> <ul> <li><code>impl Sub<SystemTime> for OffsetDateTime</code></li> <li><code>impl Sub<OffsetDateTime> for SystemTime</code></li> <li><code>impl PartialEq<SystemTime> for OffsetDateTime</code></li> <li><code>impl PartialEq<OffsetDateTime> for SystemTime</code></li> <li><code>impl PartialOrd<SystemTime> for OffsetDateTime</code></li> <li><code>impl PartialOrd<OffsetDateTime> for SystemTime</code></li> <li><code>impl From<SystemTime> for OffsetDateTime</code></li> <li><code>impl From<OffsetDateTime> for SystemTime</code></li> </ul> </li> <li> <p>All structs now <code>impl Duration<T> for Standard</code>, allowing usage with the <code>rand</code> crate. This is gated behind the <code>rand</code> feature flag.</p> </li> <li> <p>Documentation can now be built on stable. Some annotations will be missing if you do this.</p> </li> <li> <p><code>NumericalDuration</code> has been implemented for <code>f32</code> and <code>f64</code>. <code>NumericalStdDuration</code> and <code>NumericalStdDurationShort</code> have been implemented for <code>f64</code> only.</p> </li> <li> <p><code>UtcOffset::local_offset_at(OffsetDateTime)</code>, which will obtain the system's</p> </li> </ul> </tr></table> ... (truncated) </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/time-rs/time/commits/v0.2.9">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=time&package-manager=cargo&previous-version=0.1.42&new-version=0.2.9)](https://dependabot.com/compatibility-score/?dependency-name=time&package-manager=cargo&previous-version=0.1.42&new-version=0.2.9) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>