aboutsummaryrefslogtreecommitdiffstats
path: root/python/servo
diff options
context:
space:
mode:
authorbors-servo <servo-ops@mozilla.com>2021-05-22 12:31:26 -0400
committerGitHub <noreply@github.com>2021-05-22 12:31:26 -0400
commit610a8173fd6d197d03578f3b2cb2b8e1ff20ba1c (patch)
tree3b655ae9bd5d838bfe6f687852537328558e717d /python/servo
parenta6ab7c77e51cb059fbe38a53d863546d8fdb9c61 (diff)
parent08ba46a2bc1e107a4d7e148fe8c03597932e9584 (diff)
downloadservo-610a8173fd6d197d03578f3b2cb2b8e1ff20ba1c.tar.gz
servo-610a8173fd6d197d03578f3b2cb2b8e1ff20ba1c.zip
Auto merge of #28161 - servo:dependabot/cargo/bytemuck-1.5.1, r=jdm
Bump bytemuck from 1.4.1 to 1.5.1 Bumps [bytemuck](https://github.com/Lokathor/bytemuck) from 1.4.1 to 1.5.1. <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.5.1</h2> <ul> <li>Fix <code>bytes_of</code> failing on zero sized types. <a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/pull/53">PR 53</a></li> </ul> <h2>1.5</h2> <ul> <li>Added <code>pod_collect_to_vec</code>, which will gather a slice into a vec, allowing you to change the pod type while also safely ignoring alignment. <a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/pull/50">PR 50</a></li> </ul> <h2>1.4.2</h2> <ul> <li><a href="https://github.com/Kimundi">Kimundi</a> fixed an issue that could make <code>try_zeroed_box</code> stack overflow for large values at low optimization levels. <a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/pull/43">PR 43</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/Lokathor/bytemuck/commit/6f1c78e82486bcfa0da5d10970c815ec4d4a0738"><code>6f1c78e</code></a> (cargo-release) version 1.5.1</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/72d90839e50563992485efd4b5b0386d3de529a6"><code>72d9083</code></a> changelog.</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/e5d5061854e6c7a7bdecb8d82729e0406d22587c"><code>e5d5061</code></a> adjust the code to match the claims of the docs. (<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/issues/53">#53</a>)</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/b05354dc01dfbb05cd63aaa088646d2428c85c2f"><code>b05354d</code></a> (cargo-release) start next development iteration 1.5.1-alpha.0</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/e1e5ebda61d3ef5ee25e7126870ecf2a354a20d2"><code>e1e5ebd</code></a> (cargo-release) version 1.5.0</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/91777cc1aa9fad32ee49d7a6f0597880527b001d"><code>91777cc</code></a> changelog.</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/7e76723b3d769d81e5a53fb98d77d790faa7dca4"><code>7e76723</code></a> pod_collect_to_vec (<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/issues/50">#50</a>)</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/df53958735dbe39213141ac6949cc0168b46a909"><code>df53958</code></a> (cargo-release) start next development iteration 1.0.2-alpha.0</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/1cf639571b3b121ef57b7b2d02e1f2b16d6582bf"><code>1cf6395</code></a> (cargo-release) version 1.0.1</li> <li><a href="https://github.com/Lokathor/bytemuck/commit/51d68a4220ddbfe394d8fb996fdd8fff167440b6"><code>51d68a4</code></a> Include LICENSE files in published bytemuck_derive crates (<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/issues/47">#47</a>)</li> <li>Additional commits viewable in <a href="https://github.com/Lokathor/bytemuck/compare/v1.4.1...v1.5.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=bytemuck&package-manager=cargo&previous-version=1.4.1&new-version=1.5.1)](https://dependabot.com/compatibility-score/?dependency-name=bytemuck&package-manager=cargo&previous-version=1.4.1&new-version=1.5.1) 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) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details>
Diffstat (limited to 'python/servo')
0 files changed, 0 insertions, 0 deletions