-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Properties used in Maven dependencyManagement not picked up correctly #2025
Comments
It looks like this issue has been open for a while and we’ve made a bunch of improvements to Dependabot since, is this still happening, or has this problem been resolved and can we close this issue? |
Closing due to lack of user response. |
@jeffwidman Sorry for the late response, I missed the last comment. I just checked the above-mentioned sample repo again and can confirm that the issue still persists, see this log:
Dependabot is able to deduct the latest versions of the used dependencies but fails to compare them against the version that are actually used (see https://github.com/wollefitz/dependabot-maven-properties/network/dependencies). |
Just checked #6581 against your sample project and it also fixes this issue 🎉 |
Dependabot doesn't correctly pick up versions that are stored in Maven properties and used in
dependencyManagement
sections. I created a sample repository to analyze the issue a little more in-depth.dependencyManagement
block) I'm getting the following error:See also this issue Dependabot created
org.springframework.boot:spring-boot-starter-web
I'm not getting the above error anymore but Dependabot doesn't create a Pull Request to bumpproject.version.spring-boot
even though it understands that currently the latest version is2.2.4.RELEASE
:spring-boot-dependencies
was the reason for Dependabot not picking up the latest version. But when letting Dependabot run against a branch where I added an effective dependency to lombok that could be picked up directly from thedependencyManagement
block I'm still getting the same error:The text was updated successfully, but these errors were encountered: