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

  c7dbdce (
      Roll CAS Client from 5d0d03b48537 to 4967d21f2b92

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: Icae1a77c0b498820604f87f868617e6166d452c2
Commit-Queue: Recipe Roller <>
Bot-Commit: Recipe Roller <>
1 file changed
tree: 5ed7fbd9e0077362d0b02a6dd08527ba1c72eff0
  1. bin/
  2. extern/
  3. gen/
  4. go/
  5. infra/
  6. recipes/
  7. src/
  8. .gitattributes
  9. .gitignore
  10. buf.yaml
  13. OWNERS
  14. OWNERS.tse
  15. PRESUBMIT.cfg
  19. 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.