diff options
author | bors-servo <servo-ops@mozilla.com> | 2022-11-01 06:55:48 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-11-01 06:55:48 -0400 |
commit | 7772c94ac27d114dfa80cce16f5a1dce5a1e6bda (patch) | |
tree | d6341bcc5dc3e8cb89f64dd72fd4a9893737da96 | |
parent | 5bbdc3bea6458df52843d5011601a4d102913974 (diff) | |
parent | 233d7d6bf8f1b1eb3e22f143243fe436ebe16668 (diff) | |
download | servo-7772c94ac27d114dfa80cce16f5a1dce5a1e6bda.tar.gz servo-7772c94ac27d114dfa80cce16f5a1dce5a1e6bda.zip |
Auto merge of #29028 - servo:dependabot/cargo/bytemuck-1.12.2, r=jdm
chore(deps): bump bytemuck from 1.9.1 to 1.12.2
Bumps [bytemuck](https://github.com/Lokathor/bytemuck) from 1.9.1 to 1.12.2.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/Lokathor/bytemuck/blob/main/changelog.md">bytemuck's changelog</a>.</em></p>
<blockquote>
<h2>1.12.2</h2>
<ul>
<li>Fixes <code>try_pod_read_unaligned</code> bug that made it always fail unless the target
type was exactly pointer sized in which case UB <em>could</em> happen. The
<code>CheckedBitPattern::is_valid_bit_pattern</code> was being asked to check that a
<em>reference</em> to the <code>pod</code> value was a valid bit pattern, rather than the actual
bit pattern itself, and so the check could in some cases be illegally
bypassed.</li>
</ul>
<h2>1.12.1</h2>
<ul>
<li>Patch bumped the required <code>bytemuck_derive</code> version because of a regression in
how it handled <code>align(N)</code> attributes.</li>
</ul>
<h2>1.12</h2>
<ul>
<li>This minor version bump is caused by a version bump in our <code>bytemuck_derive</code>
dependency, which is in turn caused by a mixup in the minimum version of <code>syn</code>
that <code>bytemuck_derive</code> uses. See <a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/issues/122">Issue
122</a>. There's not any
specific "new" API as you might normally expect from a minor version bump.</li>
<li><a href="https://github.com/pali6">pali</a> fixed a problem with SPIR-V builds being
broken. The error handling functions were trying to be generic over <code>Display</code>,
which the error types normally support, except on SPIR-V targets (which run on
the GPU and don't have text formatting).</li>
</ul>
<h2>1.11</h2>
<ul>
<li><a href="https://github.com/WaffleLapkin">WaffleLapkin</a> added <code>wrap_box</code> and <code>peel_box</code>
to the <code>TransparentWrapperAlloc</code> trait. Default impls of these functions are
provided, and (as usual with the transparent trait stuff) you should not override
the default versions.</li>
</ul>
<h2>1.10</h2>
<ul>
<li><a href="https://github.com/TheEdward162">TheEdward162</a> added the <code>ZeroableInOption</code>
and <code>PodInOption</code> traits. These are for types that are <code>Zeroable</code> or <code>Pod</code>
<em>when in an option</em>, but not on their own. We provide impls for the various
"NonZeroINTEGER" types in <code>core</code>, and if you need to newtype a NonZero value
then you can impl these traits when you use <code>repr(transparent)</code>.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/Lokathor/bytemuck/commit/7b67524a43aeee8c8e07ad8f4486cfe81e51591c"><code>7b67524</code></a> (cargo-release) version 1.12.2</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/579950fdb52586884237c3b8c9b5584f1f3d0b1d"><code>579950f</code></a> changelog</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/12f5bfd62ecfa8b0d4b8f22080cff0685fbdfb64"><code>12f5bfd</code></a> clippy you are often a pain in my butt</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/f1571512d2f1e730f360ca7f6a2cbc9ab3c3ebef"><code>f157151</code></a> fix <code>try_pod_read_unaligned</code>... never having worked correctly (<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/issues/138">#138</a>)</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/09dd2ffd682182294a09d5874b0e255d699d833f"><code>09dd2ff</code></a> Add <code>cast_{arc,rc}</code> (and slice and try), and <code>{wrap,peel}_{arc,rc}</code>. (<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/issues/132">#132</a>)</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/950a3ed3b930a1b73f6511d2a5075940089c82b1"><code>950a3ed</code></a> use the new derive updates.</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/3f2e91d3a6a496fd93b0a7b63ab68242a65d4cd5"><code>3f2e91d</code></a> (cargo-release) version 1.2.1</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/b7b438026def815eb3b26574ef70afe75b9d685a"><code>b7b4380</code></a> derive changlog.</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/d47d527ac2b8de0544bd3c5c5ab1361be52e8de1"><code>d47d527</code></a> Fix regression <a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/issues/127">#127</a>: support <code>align</code> in <code>repr</code>s again (<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/issues/128">#128</a>)</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/995205de230338338e1c030ea82dcda116a305b5"><code>995205d</code></a> version bump</li>
<li>Additional commits viewable in <a href="https://github.com/Lokathor/bytemuck/compare/v1.9.1...v1.12.2">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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)
</details>
-rw-r--r-- | Cargo.lock | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Cargo.lock b/Cargo.lock index d397f9e8413..8331d68b798 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -512,9 +512,9 @@ checksum = "e3b5ca7a04898ad4bcd41c90c5285445ff5b791899bb1b0abdd2a2aa791211d7" [[package]] name = "bytemuck" -version = "1.9.1" +version = "1.12.2" source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "cdead85bdec19c194affaeeb670c0e41fe23de31459efd1c174d049269cf02cc" +checksum = "5aec14f5d4e6e3f927cd0c81f72e5710d95ee9019fbeb4b3021193867491bfd8" [[package]] name = "byteorder" |