| commit | 6e845989b3bc8d031e1538e8fd2c319b5e4de812 | [log] [tgz] |
|---|---|---|
| author | Adrian Taylor <adetaylor@chromium.org> | Mon Jul 08 20:51:11 2024 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jul 08 20:57:25 2024 |
| tree | da9df8c7eebff432421eb9b277e24bd65402fe26 | |
| parent | efcc6bf5700f4400e5bc5c25427c24610e9e3cd0 [diff] |
Roll serde: 1.0.203 => 1.0.204 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: * serde: 1.0.203 => 1.0.204 * serde_derive: 1.0.203 => 1.0.204 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): * serde@1.0.204, serde_derive@1.0.204: crypto-safe, safe-to-deploy, ub-risk-2 Bug: None Change-Id: I88870478c239e8f2f4f8833467f66eac36be77c7 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/+/5682927 Commit-Queue: Adrian Taylor <adetaylor@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/main@{#1324480} NOKEYCHECK=True GitOrigin-RevId: 13cd004d8d692ab8ac8a69d1dba77be178bebe40
This directory contains all third-party Rust code, and sometimes thin wrappers around it for C++ intertop.
Crates that come from crates.io are found in //third_party/rust/chromium_crates_io, and are all vendored into the Chromium git repository. They are managed through Cargo rules and with the gnrt tool. See //docs/rust.md for how to bring in new third-party libraries or update them.
The GN rules and README.chromium files for these crates are written by the gnrt tool and should not be edited by hand.
We store GN rules for each third-party crate in a directory of the same name. Under that directory a folder named based on the crate epoch version is created. This limits first-party usage of a crate to only one version within each epoch. If the crate's version has a major version greater-than 0, then that is used as its version folder, such as v1. Otherwise, the name includes all leading zeros in the version, such as v0_3.
For example, GN rules for the tutelage crate at version 1.4.3 would be stored at
//third_party/rust/tutelage/v1
Whereas GN rules for the verion 0.2.8 version would be stored at
//third_party/rust/tutelage/v0_2
Third-party Rust libraries that are not distributed through crates.io are uncommon. But they may live under //third_party/rust/crate_name directly, as a git submodule, with GN rules written for them by hand.
We do not require OWNERS in each crate's directory at this time, but this will be revisited in the future.
Rust libraries must go through the 3rd-party review process. See the review of the toml crate for an example of a Rust security review.