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/8734958060460866145

chromiumos_config:
https://chromium.googlesource.com/chromiumos/config.git/+log/689227a04dac6b3e8686d856681044b1a8dff6f0~..07e63eccac55435817cbc02ede1e34e81026ff5c
  689227a (panchok@google.com)
      provision: Add servo nexus addr in start provision request.
  07e63ec (chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com)
      centralized_suites: automatic sync from autotest

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py.git/+/8a86567fb838490fe69325488f9923fd388df52a
  8a86567 (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from 014226033c28 to a1a693f7ec8f

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: I8e3ff55de7f4e6aec464cec8f5621b8d6bd66ba9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5908580
Commit-Queue: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 56446852f4e9245e4eac0462980569ea272344da
  1. bin/
  2. extern/
  3. gen/
  4. go/
  5. infra/
  6. recipes/
  7. src/
  8. .gitattributes
  9. .gitignore
  10. buf.yaml
  11. generate.sh
  12. LICENSE
  13. OWNERS
  14. OWNERS.tse
  15. PRESUBMIT.cfg
  16. PRESUBMIT.py
  17. README.md
  18. setup_cipd.sh
  19. 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.