| commit | 4db6b06224b5ef1674ecb2598c4fb28b7fad6093 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Mon Jan 30 18:35:43 2023 -0800 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 31 02:43:23 2023 +0000 |
| tree | 82438277667fa02ce0b01d91f5e8666773f0d037 | |
| parent | fb309282f66252eb7ded2dfc5c7a9237d01dc481 [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/8790490226269963009 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/6d4c8cb85a5d7c5528e86f99eac56970c5037569 6d4c8cb (andrewlamb@chromium.org) Add profile field to ProvisionConfig. recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/895ffd7769dad9d101cfdc7dcd8ea28a4631b34c 895ffd7 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from e9c576da44c4 to c41d94e38272 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: I77e887f9bfdb0c988b943cc8b87e00aad9c4a157 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/4206726 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.