Renovate: Maven manager should not update LATEST to a version

[zbyufei]

Which Renovate are you using?

Renovate Open Source CLI

Which platform are you using?

GitHub.com

Have you checked the logs? Don't forget to include them if relevant

What would you like to do?

My github PR Demo is: https://github.com/zbyufei/mvn2releasetest/pull/1
My pom.xml is:

        <dependency>
            <groupId>org.jetbrains</groupId>
            <artifactId>annotations</artifactId>
            <version>RELEASE</version>
            <scope>compile</scope>
        </dependency>

In fact, there are still outdated maven2.x configurations such as <version>LATEST</version> and <version>RELEASE</version> in my organization and don't want to upgrade org.jetbrains:annotations from RELEASE to 20.1.0, So how to filter the version as LATEST/ RELEASE in maven not included RELEASE update

now is:

Package | Update | Change
-- | -- | --
org.apache.commons:commons-lang3 (source) | minor | 3.0 -> 3.11
org.jetbrains:annotations | minor | RELEASE -> 20.1.0
com.alibaba:fastjson | patch | 1.1.20 -> 1.1.35

but i only want:
Package | Update | Change
-- | -- | --
org.apache.commons:commons-lang3 (source) | minor | 3.0 -> 3.11
com.alibaba:fastjson | patch | 1.1.20 -> 1.1.35

[label-actions[bot]]

Please provide debug logs for this problem. Try to include only the relevant lines, e.g. for the particular dependency and/or branch that's relevant.

[label-actions[bot]]

Please do not copy paste your entire unfiltered logs. Go through the logs yourself and paste here only the parts which seem relevant.

[label-actions[bot]]

The current description of what you're trying to solve is not clear enough. Please add comments which better explain what you're trying to achieve, what's going wrong, etc.

[zbyufei]

I don't want to upgrade org.jetbrains:annotations RELEASE -> 20.1.0, how to filter the version as <version>LATEST</version> and <version>RELEASE</version> and so it disappear in the PR https://github.com/zbyufei/mvn2releasetest/pull/1

Package | Update | Change
-- | -- | --
org.apache.commons:commons-lang3 (source) | minor | 3.0 -> 3.11
org.jetbrains:annotations | minor | RELEASE -> 20.1.0
com.alibaba:fastjson | patch | 1.1.20 -> 1.1.35

[rarkins]

Thanks for the clarification. I don't think this is intended behavior and as such we should treat it as a bug. @zharinov can you confirm?

[rarkins]

@zbyufei does the problem still occur if you take away the grouping?

[zbyufei]

@zbyufei does the problem still occur if you take away the grouping?

when i take away the grouping, the problem still occur, Please see https://github.com/zbyufei/mvn2releasetest/pull/9

[viceice]

A workaround is to disable org.jetbrains:annotations dep, so renovate would never suggest any updates.

{
...
  "packageRules": [
  ...
  {
    "packageNames": ["org.jetbrains:annotations"],
    "enabled": false
  }
  ...
  ]
...
}

[zbyufei]

A workaround is to disable org.jetbrains:annotations dep, so renovate would never suggest any updates.

{
...
  "packageRules": [
  ...
  {
    "packageNames": ["org.jetbrains:annotations"],
    "enabled": false
  }
  ...
  ]
...
}

Thanks, but it is difficult to do the same standard specifications about pom.xml for each project with many developers, some project is org.jetbrains:annotations:LATEST, some project is org.jetbrains:annotations:18.0, Many packages will have this problem. So i hope maven manager should not update LATEST(RELEASE) to a version.

[viceice]

Ok, you can use matchCurrentVersion to be more explicit

  {
    "packageNames": ["org.jetbrains:annotations"],
    "matchCurrentVersion": "/^(LATEST|RELEASE)$/",
    "enabled": false
  }

[zbyufei]

Ok, you can use matchCurrentVersion to be more explicit

  {
    "packageNames": ["org.jetbrains:annotations"],
    "matchCurrentVersion": "/^(LATEST|RELEASE)$/",
    "enabled": false
  }

Thanks, but first, I must find out which packages are used "/^(LATEST|RELEASE)$/" is too difficult, because there are 5000+ repositories. and each repository has the specifications standard about pom.xml. Second packageRules is too long.

[rarkins]

@viceice perhaps we should have this in our workarounds preset until we resolve it?

  {
    "managers": ["maven"],
    "matchCurrentVersion": "/^(LATEST|RELEASE)$/",
    "enabled": false
  }

[viceice]

sure, if it works? can't test it, as i've no maven repos. 🙃

[zbyufei]

sure, if it works? can't test it, as i've no maven repos. 🙃

Thanks, and it's OK, When i add

 {
    "managers": ["maven"],
    "matchCurrentVersion": "/^(LATEST|RELEASE)$/",
    "enabled": false
  }

in packageRules, Please see my new test repository https://github.com/zbyufei/release-new-test.

[viceice]

@zbyufei Thanks for verifying, I'll post a pr to add this to our workaround soon

[rarkins]

@viceice I think @zharinov is working on a root fix for Maven anyway

[zbyufei]

https://github.com/zbyufei/release-new-test-group/ this is test case with grouping, it's also OK!
ths @viceice @rarkins
renovate is great project!!!

[renovate-release]

:tada: This issue has been resolved in version 23.86.2 :tada:

The release is available on:

• GitHub release
• 23.86.2

Your semantic-release bot :package::rocket: