renovatebot / renovate

Home of the Renovate CLI: Cross-platform Dependency Automation by Mend.io
https://mend.io/renovate
GNU Affero General Public License v3.0
17.62k stars 2.32k forks source link

Gradle missing some upgrades? #2740

Closed rarkins closed 6 years ago

rarkins commented 6 years ago

@corecanarias can you help me look into this? This question is from my fork of telegram-images.

Here's the gradle log:

       The following dependencies have later release versions:
        - com.github.rubenlagus:TelegramBots [v2.3.5 -> 2.4.4.5]
        - cglib:cglib-nodep [3.1 -> 3.2.9]
        - com.github.ben-manes:gradle-versions-plugin [0.17.0 -> 0.20.0]
        - org.codehaus.groovy:groovy [2.4.7 -> 3.0.0-alpha-3]
        - org.objenesis:objenesis [2.1 -> 3.0.1]
        - org.spockframework:spock-core [1.0-groovy-2.4 -> 1.2-RC3-groovy-2.5]
        - org.springframework.boot:spring-boot-gradle-plugin [1.4.0.RELEASE -> 2.1.0.RELEASE]
        - org.springframework.boot:spring-boot-starter-jersey [1.4.0.RELEASE -> 2.1.0.RELEASE]

But we only create these: image

These are missing:

com.github.ben-manes:gradle-versions-plugin [0.17.0 -> 0.20.0]
org.codehaus.groovy:groovy [2.4.7 -> 3.0.0-alpha-3]
org.springframework.boot:spring-boot-starter-jersey [1.4.0.RELEASE -> 2.1.0.RELEASE]

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 upgrade spring-boot-starter-plugin.

corecanarias commented 6 years ago

@rarkins Yep, that's weird. Let me take a look

corecanarias commented 6 years ago

Ok, there are two things: