mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-27 15:58:48 +00:00
a5eb22bb2f
Similar to a fix already made for gradle-wrapper, this fixes an issue with grouped dependencies leading to a wrong Java version, as `config.currentValue` may be the version of an unrelated dependency in the group rather than the version of maven itself. We can instead look up the `maven` dependency's own `currentValue` in `updatedDeps`. This does change behaviour when only `maven-wrapper` (and not `maven` itself) is being updated: previously `config.currentValue` happened to hold the wrapper's own version in that single-upgrade case, which mostly tracks the same major version as the actual Maven release. Now, with no `maven` entry in `updatedDeps` to look up, this falls back to the default Java constraint. This is deemed acceptable, as it matches the same trade-off the gradle-wrapper fix already made. Co-Authored-By: Claude Sonnet 5 <jamie.tanna+claude-code@mend.io>
Configuration for Maven Wrapper updates. Changes here affect how Renovate updates the version of Maven in the wrapper, not how it uses the wrapper.