Release
v2.9.1
clean-hands-hotfixHotfix: the direct-parent upgrade pass no longer trials a dependency whose version is supplied by an imported BOM, avoiding wasted rescans and misleading errors before it falls back to the ladder.
Highlights
- 01
Skip BOM-managed direct dependencies
A direct dependency with no <version> of its own (its version comes from an imported BOM or dependencyManagement, e.g. a Spring Cloud starter governed by spring-cloud-dependencies) is now skipped by the parent-upgrade pass instead of being trialled and erroring on a missing <version> tag.
Read the guide → - 02
Regression coverage
REG-063 asserts a versionless, BOM-managed direct dependency is skipped before any candidate trial runs, complementing REG-060's pinned-but-versioned probe-then-abandon case.
Full notes
Fixed
- Fixed the direct-parent upgrade pass selecting a BOM-managed direct dependency that has no editable <version>, which caused every movement-probe and candidate trial to error with 'failed to locate <version> tag inside dependency' before falling back to the ladder. Such dependencies are now skipped up front; the final remediation outcome is unchanged.