Not able to use renovate for bellsoft/liberica-openjdk-alpine with tag formatted with 4 blocks like :21.0.1-16

[davinkevin]

What would you like help with?

I think I found a bug

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

Github, Renovate v37.320.1-full

Please tell us more about your question or problem

Hello 👋 ,

I have the following dockerfile stored in my git repository:

FROM bellsoft/liberica-openjdk-alpine:21.0.1-16@sha256:b2cedd6b549b971e93ad1d240e72b6c69c7210664c2ddabb8b3ee504645cd71b as production
…

I first though the "default" renovate configuration would be enough to jump to 21.0.3-10.

Then, I investigated, and I've tried multiple configs, without any success.

    packageRules: [
        {
            matchDatasources: ["docker"],
            matchPackageNames: ["bellsoft/liberica-openjdk-alpine"],
            versioning: "semver"
        }
    ]

    packageRules: [
        {
            matchDatasources: ["docker"],
            matchPackageNames: ["bellsoft/liberica-openjdk-alpine"],
            versioning: "regex:^(?<major>\\d+)?(\\.(?<minor>\\d+))?(\\.(?<patch>\\d+))?(-(?<revision>.*))?$"
        }
    ]

During dry-run execution, I always see the following block:

DEBUG: packageFiles with updates (repository=gradle/dv, baseBranch=release)
       "config": {
         "dockerfile": [
           {
             "deps": [
               {
                 "depName": "bellsoft/liberica-openjdk-alpine",
                 "currentValue": "21.0.1-16",
                 "currentDigest": "sha256:b2cedd6b549b971e93ad1d240e72b6c69c7210664c2ddabb8b3ee504645cd71b",
                 "replaceString": "bellsoft/liberica-openjdk-alpine:21.0.1-16@sha256:b2cedd6b549b971e93ad1d240e72b6c69c7210664c2ddabb8b3ee504645cd71b",
                 "autoReplaceStringTemplate": "{{depName}}{{#if newValue}}:{{newValue}}{{/if}}{{#if newDigest}}@{{newDigest}}{{/if}}",
                 "datasource": "docker",
                 "depType": "final",
                 "updates": [],
                 "packageName": "bellsoft/liberica-openjdk-alpine",
                 "versioning": "regex:^(?<major>\\d+)?(\\.(?<minor>\\d+))?(\\.(?<patch>\\d+))?([\\._+](?<build>(\\d\\.?)+)(LTS)?)?(-(?<compatibility>.*))?$",
                 "warnings": [],
                 "registryUrl": "https://index.docker.io",
                 "currentVersion": "21.0.1-16",
                 "fixedVersion": "21.0.1-16"
               }
             ],
             "packageFile": "Dockerfile"
           }
         ]
       }

With the field updates: [] empty (both in dry-run or standard mode).

What is your recommendation or is there any bug with this specific version pattern? I've seen this issue, but I don't know if it's associated to my issue.

Thank you for your help!

Logs (if relevant)

Logs

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

[rarkins]

By default Renovate's docker versioning will treat anything after the - as combability, e.g. -slim. Semver versioning instead treats anything after the - as meaning it's an unstable release and to be avoided unless you're already on the same major.minor.patch-unstable. In your case you want to allow any digits after the - so I'd recommend switching to simply loose versioning as it has no concept of compatibility or of unstable.

[davinkevin]

Thank you for the answer, however after a test, it seems to not be ok.
I'm still stuck with :21.0.1-16.

My config.js has this block:

packageRules: [
        {
            matchDatasources: ["docker"],
            matchPackageNames: [
                "bellsoft/liberica-openjdk-alpine",
                "bellsoft/liberica-openjdk-alpine-musl"
            ],
            versioning: "loose"
        }
  ]

And in the log, I still have this, in dry-run mode:

       "config": {
         "dockerfile": [
           {
             "deps": [
               {
                 "depName": "bellsoft/liberica-openjdk-alpine",
                 "currentValue": "21.0.1-16",
                 "currentDigest": "sha256:b2cedd6b549b971e93ad1d240e72b6c69c7210664c2ddabb8b3ee504645cd71b",
                 "replaceString": "bellsoft/liberica-openjdk-alpine:21.0.1-16@sha256:b2cedd6b549b971e93ad1d240e72b6c69c7210664c2ddabb8b3ee504645cd71b",
                 "autoReplaceStringTemplate": "{{depName}}{{#if newValue}}:{{newValue}}{{/if}}{{#if newDigest}}@{{newDigest}}{{/if}}",
                 "datasource": "docker",
                 "depType": "final",
                 "updates": [],
                 "packageName": "bellsoft/liberica-openjdk-alpine",
                 "versioning": "regex:^(?<major>\\d+)?(\\.(?<minor>\\d+))?(\\.(?<patch>\\d+))?([\\._+](?<build>(\\d\\.?)+)(LTS)?)?(-(?<compatibility>.*))?$",
                 "warnings": [],
                 "registryUrl": "https://index.docker.io",
                 "currentVersion": "21.0.1-16",
                 "fixedVersion": "21.0.1-16"
               }
             ],
             "packageFile": "foo/Dockerfile"
           }
         ]
       }

I still see "updates": [], which means there is nothing to update.

Do you have another idea, or things I could do to bypass this issue?

[rarkins]

Per the logs, versioning is set to regex

[davinkevin]

I agree but it's not something I've set explicitly.

Is it something inherited by "extends": ["config:recommended"]? Any recommendation to investigate this?

[davinkevin]

I confirm, it's the same as this workaround.

However, shouldn't be overiden by a "local/more specific" configuration?

[davinkevin]

I did some investiongation, and with ignorePresets: ["workarounds:javaLTSVersions"], I have something better.

So I have two questions:

• is it possible to override a preset without excluding it?
• Is it a bug in the workaround?

FTR, I use this to match the versioning scheme used by liberica:

versioning: "regex:^(?<major>\\d+)(\\.(?<minor>\\d+))?(\\.(?<patch>\\d+))?(-(?<build>\\d+))?$"

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

To get started, please read our guide on creating a minimal reproduction.

Good luck,

The Renovate team