Surge of immortal PRs since 43.232.1

[famod]

How are you running Renovate?

Self-hosted Renovate CLI

Which platform you running Renovate on?

Other (please specify)

Which version of Renovate are you using?

43.235.1

Please tell us more about your question or problem

I'm using the 43 floating tag of the official Renovate image (with Jenkins and BitBucket Datacenter) and a few days ago it started omitting the concrete versions from PR titles, making many (all?) PRs effectively immortal which in turn makes it impossible to decline them.
This affects all sorts of Maven dependencies like spring boot, commons-io, smallrye-fault-tolerance, gmavenplus-plugin and others.

I digged around and found out that 43.232.1 is to blame, #43970 specifically.
It seems to me that Renovate (now?) considers everything a group that merely uses a Maven property for the version, even in cases where this property is only used for a single dependency (or plugin). Even if used for multiple dependencies, it shouldn't "auto-group".
To me this looks like an unwanted side-effect / regression.

Gemini suggested to do something like this (maybe with a more sophisticated pattern) but I have a very hard time accepting that this is the way forward for such really standard (read: best practice) Maven setups:

{
  "packageRules": [
    {
      "matchPackagePatterns": ["*"],
      "groupName": null,
      "recreateClosed": false
    }
  ]
}

Presets in place:

    "group:monorepos",
    "group:recommended",
    "mergeConfidence:age-confidence-badges",
    "replacements:all",
    "security:minimumReleaseAgeNpm",
    "workarounds:all"

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

PS: I had to edit this discussion because I first wrongly stated that 43.233.0 is to blame but it really is 43.232.1.

[Chrimle]

+1 on the "considers everything a group that merely uses a Maven property for the version", now it says:

Bump some-dependency.version (major)

Instead of

Bump groupId:some-dependency v1 -> v2

(Does not respect the commitMessageExtra)

[felipecrs]

Is this the only case where you guys can reproduce the issue? With Maven properties?

[felipecrs]

If yes, should be fixed by:

• fix: preserve version in PR title for Maven property updates #44176

[ext]

I've just had this happen with NPM as well, some examples:

chore(deps): update font awesome (major) (gitlab, self hosted runner)
chore(deps): update @forsakringskassan/jest-config monorepo (major) (github, cloud)

Both turned immortal after being previously closed.

[famod]

Is this the only case where you guys can reproduce the issue? With Maven properties?

I don't have a gradle project at hand, but Gemini was telling me that gradle properties are affected as well (take this with a grain of salt).

[edgarvonk]

We have this issue both for NPM and Gradle dependencies.

PS: we are not using a self-hosted Renovate. We are using the official Renovate GitHub App. So maybe I am posting this in the wrong issue..

[felipecrs]

For Gradle properties #44176 should do the trick as well. I'll investigate for NPM.