[7.1.0] Allow @repo_name
labels in override attributes
#21314
Closed
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 is made possible by a refactoring that moves the label parsing of
RepoSpec
attributes coming from module overrides as well as.bzl
file labels containing repo rules fromBzlmodRepoRuleFunction
intoModuleFileGlobals
. Also adds a TODO toBzlmodRepoRuleFunction
to further simplify the logic after the next lockfile version bumps, as old lockfiles are now the only source of non-canonical labels inRepoSpec
s.Work towards #19301
Closes #21188.
Commit f0ab82d
PiperOrigin-RevId: 605517195
Change-Id: Id34c81fa9474fef2354ff1fbc898e518a9044640