| commit | 050d12a8c4d7cf72aadbbcc71a3d1752f0c1f0a4 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Sat Apr 13 01:05:36 2024 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Apr 13 01:13:24 2024 |
| tree | bccfc907a4fde540ec6665c18a57b79c8d0dc5fb | |
| parent | 666328259b5c0c8f9f7ce7bc383a639c6a2c7051 [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/8750814416691220833 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/89f020148f6aa7899821f1b859a4eb5532a5c401 89f0201 (jstanko@google.com) DutTopology: add cellular carrier recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/00ae0edcf18f8fc84fee4d9d8cdcbed899435895 00ae0ed (mohrr@google.com) [config_types.Path] Add parents property 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: I9548b8b39020134a599dee166c4836d1906082d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/5450870 Bot-Commit: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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.