Closed rarkins closed 6 years ago
@rarkins Yep, that's weird. Let me take a look
Ok, there are two things:
gradle-versions-plugin It's because we are using the recommended version for gradle-use-latest-versions-plugin 0.2.3 Last week they release a new version: 0.2.5 and now in the docs says using 0.20.0 Probably we would need a way to maintain this dependencies up to date as well. But not sure how, since this is an internal configuration of renovate. Maybe externalize it to the dockerfile? But that would introduce more complexity for someone that wants to run it without docker
For the other two dependencies, it's not updated because they are defined without versioning:
compile('org.springframework.boot:spring-boot-starter-jersey')
compile('org.codehaus.groovy:groovy')
This dependencies are selected based on spring-boot-gradle-plugin version. So they will automatically pick the latest version when this version changes.
@corecanarias can you help me look into this? This question is from my fork of telegram-images.
Here's the gradle log:
But we only create these:
These are missing:
The first one is the one we inject, right? Should we be using the latest version of it?
groovy looks to be an "unstable" version so maybe that's why it's skipped? But then why are we upgrading spock-core to a stable version instead of
1.2-RC3-groovy-2.5
?Also I can see no reason for skipping
spring-boot-starter-jersey
's upgrade as we alreaduy upgradespring-boot-starter-plugin
.