| commit | fdb4c6561e9eba8f604af7fa187b7850fddf8076 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Thu May 09 20:13:44 2024 -0700 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 10 03:21:23 2024 +0000 |
| tree | dad3a330f8ba824ca7eadb223640fb3d5b544172 | |
| parent | 55980c44ef6286ac60eab6f2322a54fef8ed0f57 [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/8748360120206908449 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/47a4ec121b6ee623e84ea698b6a5c9afeef6e3d7 47a4ec1 (chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com) centralized_suites: automatic sync from autotest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/61d032078b9e8f1a9a512bbaed668224deedca9d 61d0320 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 1e5bc7b60694 to 0353d07d5ede 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: Iff92c50d40c0089fe0822596e683bc1aed34d1e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5531062 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.