| commit | 4f9f56943aa78a49934ea0b87a8d99f145137795 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Fri Sep 29 16:31:35 2023 -0700 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 29 23:38:19 2023 +0000 |
| tree | 0174a1452d50bea5fbef93c4ebc13b03a77e4a0d | |
| parent | 8ecf51a7879e8c5dac62a668e0a1e43bee8ee941 [diff] |
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/8768577085982638737 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/35d664d35c5d92a51c3f4c23d9a94b838ee01e7e 35d664d (sammc@chromium.org) Add ResourceConfig as a platform and SoC topology config. recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/d6b82b7cd8f8794ee6785df69e505db351a0e37e d6b82b7 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 2c2d4e4ba852 to 4d1a67cc1301 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: Iae56988f8b4dbdcd6b0c0003df826bc8f31ccc13 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/4904940 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.