Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls
recipe changes from upstream projects (recipe_engine) into this repository.

The build that created this CL was
https://ci.chromium.org/b/8819496977853676225

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py.git/+/c827c1b6bbdd42908581cc6518c3f193ce33a21a
  c827c1b (chanli@chromium.org)
      Revert "[recipe-py] buildbucket: enable buildbucket tracking pa...

More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug.

R=ayatane@chromium.org

Recipe-Tryjob-Bypass-Reason: Autoroller
Ignore-Freeze: Autoroller
Bugdroid-Send-Email: False
Change-Id: I772c9b335042cb9824995e6c298ecbd58f588aa0
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/3531077
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: 69611060e17b2818d54c24d914d6f076cb39f0eb
  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.