| commit | 87c3acc2bd116a27dad3213010bc902ae8141bad | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Sat Nov 02 00:51:34 2024 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Nov 02 00:58:36 2024 |
| tree | b4577d6703b886fc122e373b658c8118c4c6da80 | |
| parent | 1f571c0473ebbce531b0340855b9d622cc9fb221 [diff] |
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/8732423863356724833 recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/1514d0e5c656bce369b99a887d2b5854f8913d12 1514d0e (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from cf8fe0578461 to a529ac2ad3a2 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: I124579f512e5f51c0aace74d7a8898f4d7e5aa83 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5985424 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>
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.