commit | 0124c7a1ad190339451b97d94c1b7b966b653043 | [log] [tgz] |
---|---|---|
author | Lukasz Anforowicz <lukasza@chromium.org> | Mon Jun 24 23:57:14 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 24 23:57:14 2024 |
tree | 1fd7e983dc9e4aab1641b55744ad1ba6821a5261 | |
parent | 9fb9c6af8d47cf0fae6200709c198eb19d554d75 [diff] |
Roll bytemuck: 1.16.0 => 1.16.1 in //third_party/rust. This CL has been created semi-automatically. The expected review process and other details can be found at //tools/crates/create_update_cl.md Updated crates: * bytemuck: 1.16.0 => 1.16.1 Chromium `supply-chain/config.toml` policy requires that the following audit criteria are met (note that these are the *minimum* required criteria and `supply-chain/audits.toml` can and should record a stricter certification if possible; see also //docs/rust-unsafe.md): * bytemuck@1.16.1: crypto-safe, safe-to-deploy, ub-risk-2 Bug: None Change-Id: Id6a8c5b9be9afab263f84b5ca22bb0ff256b6886 Cq-Include-Trybots: chromium/try:android-rust-arm32-rel Cq-Include-Trybots: chromium/try:android-rust-arm64-dbg Cq-Include-Trybots: chromium/try:android-rust-arm64-rel Cq-Include-Trybots: chromium/try:linux-rust-x64-dbg Cq-Include-Trybots: chromium/try:linux-rust-x64-rel Cq-Include-Trybots: chromium/try:win-rust-x64-dbg Cq-Include-Trybots: chromium/try:win-rust-x64-rel Disable-Rts: True Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5650895 Auto-Submit: Ćukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Adrian Taylor <adetaylor@google.com> Reviewed-by: Adrian Taylor <adetaylor@google.com> Cr-Commit-Position: refs/heads/main@{#1318877}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.