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

chromiumos_config:
https://chromium.googlesource.com/chromiumos/config.git/+log/4591475a3f2af327a788ff4d57785c17b6be4db0~..66789675820c856e6d5840737a9d2c663b9c8e81
  4591475 (zhihuixie@google.com)
      infra proto: add a lint rule LINT.IfChange to TestHarness proto
  f7c8293 (chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com)
      centralized_suites: automatic sync from autotest
  6678967 (hsueh.rasheed@inventec.corp-partner.google.com)
      config: add ALC3247 codec to topology

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py.git/+/18066dfae0089fafc198db98a03ca5f571826363
  18066df (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from b4788deffcd4 to 69f852c6aea2

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: Ic8b5969063bf3bd9764ab8f113a807659a3e8792
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5513065
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: b1716ff7e061585e74dfc5a2e2b42a4a9b3ef094
  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.