Renovate: commons-beanutils problems with versioning and renovate

[haarchri]

docker runner: renovate/renovate:23.15.0
self-hosted via gitlab

It looks like common-beanutils has very old version numbers - but it breaks all our builds
https://mvnrepository.com/artifact/commons-beanutils/commons-beanutils

        <dependency>
            <groupId>commons-beanutils</groupId>
            <artifactId>commons-beanutils</artifactId>
            <version>20030211.134440</version> <-- renovate update to this version
            <version>1.9.4</version> <-- what we would expect
            <version>1.9.3</version> <-- our configured version
        </dependency>

any ideas to configure a rule or is it possible to fix - or check also the date of the specific version

[rarkins]

A package rule with "allowedVersions": "!/^2003/" and matching that package name should exclude it. We can also add it to our workarounds preset.

[haarchri]

for me it looks like we need a solution for lot of renovate installation - is it possible to add it to the workarounds preset ?

[rarkins]

If packages have problematic versions that should be ignored and such rules would benefit anyone using it then yes

[JamieMagee]

@zharinov didn't you fix a similar issue for another Apache commons package recently? Should we also add this package to the workarounds preset?

[zharinov]

Will make generic workaround soon

[rarkins]

One idea is we could have logic that a version must be "greater than" but also "newer than" according to the release. But for example if versions are released in this order then that would break:

• 1.5.0
• 2.0.0
• 1.5.1

[renovate-release]

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

The release is available on:

• GitHub release
• 23.89.1

Your semantic-release bot :package::rocket: