Published package version scheme differences Break Automated Updates

[TiKevin83]

There are some oddities in package versions published that break our Renovate automatic update process - one labeled 2023-01-24T02-11-56-babda5f is always detected by renovate as the latest version "2023" ahead of the actual most recent version "22".

[dondonz]

Hello, thanks for reporting.

We've since made a change to start master build versions with the prefix 0.0.0 then followed by the timestamp, which will prevent future releases creating this Renovate problem.

Unfortunately that doesn't solve your exact problem of the version starting with 2023 already released. I use Renovate as well so I know it's quite annoying, sorry about that. Sadly it's not possible to delete old versions off Maven.

Instead, could you try adding a rule to exclude these poorly named versions from Renovate?