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
https://ci.chromium.org/b/8792226033539524641

chromiumos_config:
https://chromium.googlesource.com/chromiumos/config.git/+log/53b0e081acc141d6626bf40ed7ea7341854020b5~..f92c036069a42c258985eca407b301bbc9dcfa84
  53b0e08 (jeffrj_wang@compal.corp-partner.google.com)
      Add definition for audio amplifier NAU8318
  f92c036 (bniche@google.com)
      [fleet-cft] [fleet-chameleon] update chameleon dut topology

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py.git/+/573a3a6797dba8011d482e6756860bdb894339ba
  573a3a6 (randymaldonado@google.com)
      [recipes-py] passing debugging experiment to children in placeh...

Please check the following references for more information:
- autoroller, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#autoroller
- rollback, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#rollback
- cross-repo dependencies, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/cross_repo.md

Use https://goo.gl/noib3a to file a bug.

Recipe-Tryjob-Bypass-Reason: Autoroller
Ignore-Freeze: Autoroller
Bugdroid-Send-Email: False
Change-Id: Ia07559828930fdfaa64275bc0caa1065f7f3b430
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/4158413
Bot-Commit: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 157eae0df2939da5988e7046d4e3a634318a7400
  1. extern/
  2. gen/
  3. go/
  4. infra/
  5. recipes/
  6. src/
  7. .gitattributes
  8. .gitignore
  9. buf.yaml
  10. generate.sh
  11. LICENSE
  12. OWNERS
  13. PRESUBMIT.cfg
  14. PRESUBMIT.py
  15. README.md
  16. setup_cipd.sh
  17. unblocked_terms.txt
README.md

infra/proto

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.