fix: get BCR publishing working by upgrading rules_go - #1278
Merged
Conversation
Recent BCR deployments have been failing, like this one for 3.7.0 for example: bazelbuild/bazel-central-registry#9894 It appears to be because e2e/smoke is on an older version of rules_go that is missing this fix required for newer Bazel versions: bazel-contrib/rules_go#4508 We're only hitting this issue on BCR deployment because for BCR we make rules_go a dev_dependency in the top-level MODULE.bazel, causing rules_go to use the older version from e2e/smoke/MODULE.bazel. This should fix bazel-contrib#1277.
jbedard
approved these changes
Jul 31, 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
2 participants
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.
Recent BCR deployments have been failing, like this one for 3.7.0 for example: bazelbuild/bazel-central-registry#9894
It appears to be because e2e/smoke is on an older version of rules_go that is missing this fix required for newer Bazel versions: bazel-contrib/rules_go#4508
We're only hitting this issue on BCR deployment because for BCR we make rules_go a dev_dependency in the top-level MODULE.bazel, causing rules_go to use the older version from e2e/smoke/MODULE.bazel.
This should fix #1277.