Revert "Update prebuilts for the new snapshot"

This reverts commit 048f9a0684fa373f2f2df5fb79b1f6a9ad902d91.

Reason for revert: I thought the file was stale but it is up to date thanks to

Original change's description:
> Update prebuilts for the new snapshot
> BUG=b:262460834
> TEST=BOARD=amd64-generic bazel build --config=prebuilts/amd64-generic \
>      //bazel/images:chromiumos_base_image
> Change-Id: I8af78eb1ab43129f16db8c813e35cdac199c20ed
> Reviewed-on:
> Auto-Submit: Shuhei Takahashi <>
> Tested-by: Shuhei Takahashi <>
> Commit-Queue: Shuhei Takahashi <>
> Commit-Queue: Matt Stark <>
> Reviewed-by: Matt Stark <>

Bug: b:262460834
Change-Id: Ie0864a41b12206303033795714be2d8edf6a658f
Reviewed-by: Matt Stark <>
Commit-Queue: Shuhei Takahashi <>
Bot-Commit: Rubber Stamper <>
1 file changed
tree: 6f66fcb3e8e7467d4b27bee6eb8258c96ff373a6
  1. bazelrcs/
  2. cros/
  3. platforms/
  4. test/
  5. third_party/
  6. toolchains/
  7. workspace_root/
  8. .bazelrc
  9. .gitignore
  10. common.bazelrc
  13. OWNERS
  14. OWNERS.clover
  17. WORKSPACE.cros

Chrome OS Bazel Rules


This repository provides common rules and configuration for Bazel projects in Chrome OS.


The code is this directory is experimental and under active development. Stability and functionality is not guaranteed :)

Configuring dev experience


We use rust_analyzer to generate a rust-project.json file in the workspace root, which allows vscode to understand your dependencies.

Simply install the rust_analyzer VSCode plugin, and then add the following to your .vscode/tasks.json file, substituting TARGET for a label of any bazel target you want to depend on. VSCode will then analyze all the transitive dependencies of the specified targets.

For example, I might use the following line:

"args": ["run", "//rules_cros/toolchains/rust:gen_rust_project", "--", "//rules_cros/toolchains/rust/examples/use_local_crate/...", "//rules_cros/toolchains/rust/examples/hello_world:helllo_world"],

    "version": "2.0.0",
    "tasks": [
            "label": "Generate rust-project.json",
            "command": "bazel",
            "args": ["run", "//rules_cros/toolchains/rust:gen_rust_project", "--", "<TARGET1>", "<TARGET2>", "..."],
            "options": {
                "cwd": "${workspaceFolder}"
            "group": "build",
            "problemMatcher": [],
            "presentation": {
                "reveal": "never",
                "panel": "dedicated",
            "runOptions": {
                "runOn": "folderOpen"

If you add a new file, you may need to manually re-run the task.