Skip to content
Snippets Groups Projects
Unverified Commit 431cfc2e authored by bors[bot]'s avatar bors[bot] Committed by GitHub
Browse files

Merge #568

568: Bump time from 0.3.16 to 0.3.17 r=mkroening a=dependabot[bot]

Bumps [time](https://github.com/time-rs/time) from 0.3.16 to 0.3.17.
<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.3.17</h2>
<p>See the <a href="https://github.com/time-rs/time/blob/main/CHANGELOG.md">changelog</a> for details.</p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/time-rs/time/blob/main/CHANGELOG.md">time's changelog</a>.</em></p>
<blockquote>
<h2>0.3.17 [2022-11-06]</h2>
<h3>Changed</h3>
<ul>
<li>The amount of code generated by <code>time::serde::format_description!</code> is reduced if not all feature
flags are active.</li>
<li><code>cargo test --tests</code> works with any configuration of feature flags. This occurs by spawning a
subprocess that passes <code>--all-features</code>. <code>cargo test --doc</code> works with most combinations of
feature flags, including the default. The combination of these changes means that crater will now
run on <code>time</code>.</li>
<li><code>libc</code> and <code>num_threads</code> are only included as dependencies when needed. They were previously
unconditionally included.</li>
</ul>
<h3>Added</h3>
<ul>
<li><code>time::format_description::parse_owned</code>, which returns an <code>OwnedFormatItem</code>. This avoids &quot;lifetime
hell&quot;, where all your structs now need a lifetime because a single field has one. Note that when
possible, the borrowed format item (just called <code>FormatItem</code>) is still preferred, as it has
significantly fewer allocations. The new <code>OwnedFormatItem</code> is usable for both formatting and
parsing, as you would expect.</li>
</ul>
<h3>Compatibility</h3>
<ul>
<li>The parser for runtime format descriptions has been rewritten. A side effect of this is that some
errors have slightly changed. No existing API has been altered, so this is not a breaking change.
However, you may notice different errors, which are hopefully better! The parser for compile-time
format descriptions has not yet been swapped out. If you notice any bugs, please file an issue.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/time-rs/time/commit/d97594b9f5cfeab0335c16687e26a8b51c56a526"><code>d97594b</code></a> 0.3.17 release</li>
<li><a href="https://github.com/time-rs/time/commit/88f5c134f3c55465f896a806c267c664280bda40"><code>88f5c13</code></a> Fix concurrency for GitHub actions</li>
<li><a href="https://github.com/time-rs/time/commit/e5e2a601880a63dc28a657c31aea156d470d510b"><code>e5e2a60</code></a> Update lints</li>
<li><a href="https://github.com/time-rs/time/commit/27ea0d44f46c2875ea121ccbb0fec1b844531194"><code>27ea0d4</code></a> Use <code>parse_owned</code> in tests</li>
<li><a href="https://github.com/time-rs/time/commit/4887aa7c43465296e959766d15a4e97e9da2d339"><code>4887aa7</code></a> Add <code>format_description::parse_owned</code></li>
<li><a href="https://github.com/time-rs/time/commit/2ba92f67b1d55389c6a6692557428c2dbe58c0be"><code>2ba92f6</code></a> Configure codecov</li>
<li><a href="https://github.com/time-rs/time/commit/2cba2ef2f56db69f31bab953ba217b825875d208"><code>2cba2ef</code></a> Add tests for <code>OwnedFormatItem</code></li>
<li><a href="https://github.com/time-rs/time/commit/4d18c08d8e3d6411370e888374ae580e026544c4"><code>4d18c08</code></a> Implement owned format descriptions</li>
<li><a href="https://github.com/time-rs/time/commit/139aba1460f142b06eace74bc176ab7113dd9521"><code>139aba1</code></a> Move <code>FormatItem</code> definition to its own module</li>
<li><a href="https://github.com/time-rs/time/commit/e4b40add3fe4ecadc5ef9345e0233e06dfb5d233"><code>e4b40ad</code></a> Remove extraneous debug call</li>
<li>Additional commits viewable in <a href="https://github.com/time-rs/time/compare/v0.3.16...v0.3.17">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=time&package-manager=cargo&previous-version=0.3.16&new-version=0.3.17)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores

)

You can trigger a rebase of this PR 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)


</details>

Co-authored-by: default avatardependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
parents 44db529d 3786a2a0
Branches
Tags
Loading
Checking pipeline status
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment