Skip to content

ci: resolve Envoy proto dependencies from API lockfile - #526

Merged
rulex123 merged 5 commits into
envoyproxy:mainfrom
rulex123:fix/envoy-module-dependency-revisions
Nov 2, 2026
Merged

rulex123 merged 5 commits into
envoyproxy:mainfrom
rulex123:fix/envoy-module-dependency-revisions

Conversation

@rulex123

@rulex123 rulex123 commented Oct 30, 2026 •

Copy link
Copy Markdown
Collaborator

The daily proto updater fails for Envoy v1.40.2 because Envoy removed api/bazel/repository_locations.bzl during its migration to Bazel modules.

Read api/MODULE.bazel.lock at the requested Envoy revision, find each dependency's registry source.json, and extract its source tag or commit from the archive URL. Preserve the existing API_SHAS format and downloader.

Keep CEL explicitly pinned to 0.25.1. The API lockfile selects 0.24.0 after Envoy removed its direct CEL requirement; following that selection would downgrade proto definitions we already ship and change generated CEL conformance APIs. The other five dependencies follow the API lockfile.

Observed failure: https://github.com/envoyproxy/java-control-plane/actions/runs/40855490255/job/123385334334

Signed-off-by: rulex123 <erica.manno@gmail.com>
Signed-off-by: rulex123 <erica.manno@gmail.com>
Signed-off-by: rulex123 <erica.manno@gmail.com>
Signed-off-by: rulex123 <erica.manno@gmail.com>
@rulex123 rulex123 changed the title ci: resolve Envoy proto dependencies from Bazel lockfile ci: resolve Envoy proto dependencies from API lockfile Nov 2, 2026
Signed-off-by: rulex123 <erica.manno@gmail.com>
@rulex123
rulex123 merged commit dc59a93 into envoyproxy:main Nov 2, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant