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

chromiumos_config:
https://chromium.googlesource.com/chromiumos/config.git/+log/4ae3e41912c1f0d6a857c7be700df6fc1c6343b8~..571d0707d2504a3327096be5871f9da3d0bca9cd
  4ae3e41 (dbeckett@chromium.org)
      test_suite proto: add testcaseList
  47340d5 (mingkong@google.com)
      Move cros-tool-runner v2 API definitions to the common place
  f455d38 (rrangel@chromium.org)
      config: Add sampling_rate to OndemandGovernor
  571d070 (ddavenport@chromium.org)
      Add SEAMLESS_REFRESH_RATE_SWITCHING to DisplayPanel

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py.git/+/e57338e3daf0ba532f2b29e369ab5d6ba4a503ba
  e57338e (iannucci@chromium.org)
      [luciexe] Update engine to emit build streams with MergeBuild.

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: Ife78019f92dda2613fa6edb7034aa1a901d6c474
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3778406
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: d34a0da53df1fab674f5dda026823007a3f565fb
  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.