Draft
Conversation
Co-authored-by: phlax <454682+phlax@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Rename io_bazel_rules_go to rules_go for consistency
bazel: rename io_bazel_rules_go to rules_go
Aug 24, 2026
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.
This updates Envoy’s last major pre-bzlmod repository rename from
io_bazel_rules_gotorules_go, matching the BCR module name. The change also preserves WORKSPACE-era compatibility for transitive deps that still hardcode@io_bazel_rules_go.Repository rename + metadata alignment
io_bazel_rules_gotorules_go.rules_goas the canonical key while retaining the legacy apparent name where dependency metadata expects it.repo_name = "io_bazel_rules_go"override inapi/MODULE.bazelso bzlmod usesrules_godirectly.Direct label migration
@io_bazel_rules_go//...to@rules_go//....contrib/and related test fixtures.WORKSPACE-side compatibility shims
_go_deps()backward-compatible with bothio_bazel_rules_goandrules_goinskip_targets.repo_mapping = {"@io_bazel_rules_go": "@rules_go"}to external repos known to consume rules_go transitively, including:gazellerules_proto_grpcgoogleapiscom_envoyproxy_protoc_gen_validatecom_github_chrusty_protoc_gen_jsonschemago_repository(...)declarations in root and mobile dependency macrosGenerated / injected repo fixes
@rules_go.rules_gopatch so WORKSPACE-generated toolchain/dependency repos emit@rules_goinstead of@io_bazel_rules_go.googleapispatch so its generated imports repo resolves Go rules through@rules_goas well.Example of the label transition applied throughout the tree: