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

chromiumos_config:
https://chromium.googlesource.com/chromiumos/config.git/+log/d2c21dda6baec59fe36a2b94696ec69678fe514a~..aa67db9f42caed1029a1df03c4ffec8a2dd8fb1d
  d2c21dd (bbrotherton@google.com)
      suite_sets: update PVS suite sets
  f1af7db (bbrotherton@google.com)
      suite_sets: replace labqual with labqual_stable
  5140a72 (aamirbohra@google.com)
      checker: Remove get_program helper function
  98ffc06 (chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com)
      centralized_suites: automatic sync from autotest
  aa67db9 (peggy.chen@cienet.com)
      config: Remove fw_rw_active_version from topology.proto

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py.git/+/b667a7fdd742492783872c260e48f18eaf6507c8
  b667a7f (mohrr@google.com)
      [misc] Add path-migration scripts

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: I84bd092a720b9480f3cac514cf4b4310917ad6e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5535561
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: c5ca38bf696f27dac575cea98c35c1af072eb096
  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.