| commit | b1df34102d968b61567c06f36b1db10fe14fe877 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Wed Nov 05 21:53:58 2025 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 05 22:01:18 2025 |
| tree | 87ffc0a2195e88e90b765fefb8b62cf9977c0054 | |
| parent | 8fa38013dbc9a6cd5db98466bfc73499c02a345d [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/8699004906500448609 chromiumos_config: https://chromium.googlesource.com/chromiumos/config.git/+/ccf48c19be3a8da905fa9670142c31012ba199ce ccf48c1 (andrewlamb@google.com) cros_to_android: Add generate-component-xmls subcommand. recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/b2ab5f39fa6f3b4d44e069e3da9009e3050f89eb b2ab5f3 (mohrr@google.com) [engine] Don't catch cancellations in except 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: I0cf7f132ca34065263f3f046c9b0174680865178 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/7125164 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.