Fix resolver BOM force versions#1571
Draft
shs96c wants to merge 1 commit into
Draft
Conversation
shs96c
force-pushed
the
shs/bom-force-version
branch
3 times, most recently
from
May 13, 2026 10:21
13299bd to
a768256
Compare
shs96c
changed the title
shs96c
force-pushed
the
shs/bom-force-version
branch
from
May 13, 2026 11:52
a768256 to
a1b1cef
Compare
shs96c
force-pushed
the
shs/bom-force-version
branch
4 times, most recently
from
June 9, 2026 14:39
99ccdc5 to
79221bf
Compare
Preserve force_version metadata for BOMs through Bzlmod extension processing, resolver config parsing, and duplicate BOM resolution. Share artifact/BOM merge helpers while keeping their resolver inputs separate, and add regression coverage for request metadata, Gradle script rendering, and Maven/Gradle resolver behavior.
shs96c
force-pushed
the
shs/bom-force-version
branch
from
June 11, 2026 11:37
79221bf to
aa533b8
Compare
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
1 participant
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 resolvers accept BOMs from
MODULE.bazeland version catalogs, butamend_artifact(force_version = ...)andversion_conflict_policy = "pinned"did not consistently preserve forced BOM versions through resolution. This allowed higher transitive BOM versions, or an earlier duplicate requested BOM, to win silently.What
amend_artifactmatch BOM declarations as well as artifact declarationsforce_versionmetadata before repo mergingforce_versionthroughResolverConfigstrictlyplusresolutionStrategy.forceMavenResolverGenerated with Codex