Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls
recipe changes from upstream projects (chromiumos_config, recipe_engine) into this repository.

The build that created this CL was

  e6b0825 (
      Install apm.ini files as part of topology-level cras config files.
  a949ebc (
      Add a config DesignId override to DesignId to dedupe software c...
  00d230e (
      plan.proto: Add VMTestPlan proto.
  f5859b1 (
      nnpalm: Add nnpalm config

  bb1fb5a (
      [python] Set warning for entire python module.

More info is at Use to file a bug.

Recipe-Tryjob-Bypass-Reason: Autoroller
Ignore-Freeze: Autoroller
Bugdroid-Send-Email: False
Change-Id: Id94da9a063b79845e808f2bbe6c9c5d861fd6004
Commit-Queue: Recipe Roller <>
Bot-Commit: Recipe Roller <>
1 file changed
tree: 09c875bff4ac62b591a207df7b02d8c64f47d9b0
  1. extern/
  2. gen/
  3. go/
  4. infra/
  5. recipes/
  6. src/
  7. .gitattributes
  8. .gitignore
  9. buf.yaml
  12. OWNERS
  13. PRESUBMIT.cfg
  17. unblocked_terms.txt


infra/proto vs chromite/infra/proto

This repository exists in two locations in the tree: infra/proto, and chromite/infra/proto. The infra/proto repository is always at ToT, while the chromite/infra/proto checkout is branched to allow the proto there to (more) accurately reflect the version of the proto the Build API is using.

When making changes to the proto that you need to test in the Build API, you will need ensure the changes are applied to the chromite/infra/proto checkout. Chromite generates its proto bindings from the chromite/infra/proto repo.