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

  ee2fea4 (
      [file] Clean up some py2 compatibility things.

Please check the following references for more information:
- autoroller,
- rollback,
- cross-repo dependencies,

Use to file a bug.

Recipe-Tryjob-Bypass-Reason: Autoroller
Ignore-Freeze: Autoroller
Bugdroid-Send-Email: False
Change-Id: I0d364f11c8ff5c966da7598a9a1809371315a393
Bot-Commit: Recipe Roller <>
Commit-Queue: Recipe Roller <>
1 file changed
tree: 7b6af283f0b8d37a8271636d6dce7356cfbcbd81
  1. extern/
  2. gen/
  3. go/
  4. infra/
  5. recipes/
  6. src/
  7. .gitattributes
  8. .gitignore
  9. buf.yaml
  12. OWNERS
  13. OWNERS.tse
  14. PRESUBMIT.cfg
  18. unblocked_terms.txt


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.