| commit | 9fa8b4e3bf5ffb247d67422a4eeeb8b8a5291b77 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com> | Thu Nov 06 00:42:19 2025 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 06 00:49:19 2025 |
| tree | 12ae24e94a59be2be109d57155a0a5f68e809ec6 | |
| parent | 7d3850b39675ee6385f68e150f894de4308c6c4e [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (recipe_engine) into this repository. The build that created this CL was https://ci.chromium.org/b/8698994211156802945 recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py.git/+/434dc62b928b964968e9b4051533ddaa055e5d52 434dc62 (mohrr@google.com) Revert "[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: Iee604ce10ce98f6c7ed6e6bb2c68c673673e3263 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/7125113 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.