Repository navigation
ci: resolve Envoy proto dependencies from API lockfile - #526
Merged
rulex123 merged 5 commits intoNov 2, 2026
Merged
Conversation
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>
Signed-off-by: rulex123 <erica.manno@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The daily proto updater fails for Envoy v1.40.2 because Envoy removed
api/bazel/repository_locations.bzlduring its migration to Bazel modules.Read
api/MODULE.bazel.lockat the requested Envoy revision, find each dependency's registrysource.json, and extract its source tag or commit from the archive URL. Preserve the existingAPI_SHASformat 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