How to stop changing docker major version to major.minor.patch version?

[nitrocode]

What would you like help with?

I would like help with my configuration

How are you running Renovate?

Mend Renovate hosted app on github.com

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

No response

Please tell us more about your question or problem

I have a Dockerfile that's using 21-jre of a version tag and renovate is trying to change it to 21.0.4-jre.

How can I stop this from happening?

I'd rather, for now, only bump major versions with Docker and never pin the minor and patch versions so the container will always be latest when it builds. I understand that isn't best practice. The org I'm in isn't ready for this level of pinning yet.

Logs (if relevant)

N/A

[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.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

Good luck,

The Renovate team

[nitrocode]

In the docs, it says

Renovate does not yet support "pinning" an imprecise version to a precise version, e.g. from myimage:1.2 to myimage:1.2.0, but it's a feature we'd like to work on one day.

But I see this in renovate which migrates a value of 21-jre to 21.0.4-jre

               {
                 "depName": "azul/zulu-openjdk-alpine",
                 "currentValue": "21-jre",
                 "replaceString": "azul/zulu-openjdk-alpine:21-jre",
                 "autoReplaceStringTemplate": "{{depName}}{{#if newValue}}:{{newValue}}{{/if}}{{#if newDigest}}@{{newDigest}}{{/if}}",
                 "datasource": "docker",
                 "depType": "final",
                 "updates": [
                   {
                     "bucket": "non-major",
                     "newVersion": "21.0.4-jre",
                     "newValue": "21.0.4-jre",
                     "releaseTimestamp": "2024-08-29T04:34:20.415Z",
                     "newMajor": 21,
                     "newMinor": 0,
                     "newPatch": 4,
                     "updateType": "patch",
                     "branchName": "renovate/azul-zulu-openjdk-alpine-21.x"
                   }
                 ],
                 "packageName": "azul/zulu-openjdk-alpine",
                 "versioning": "regex:^(?<major>\\d+)?(\\.(?<minor>\\d+))?(\\.(?<patch>\\d+))?([\\._+](?<build>(\\d\\.?)+)(LTS)?)?(-(?<compatibility>.*))?$",
                 "warnings": [],
                 "registryUrl": "https://index.docker.io",
                 "currentVersion": "21-jre",
                 "currentVersionTimestamp": "2023-10-18T10:02:18.182Z",
                 "isSingleVersion": true,
                 "fixedVersion": "21-jre"
               }

Is this a bug?

I tried this packageRule as well with no luck

    {
      "enabled": true,
      "matchDatasources": [
        "docker"
      ],
      "matchUpdateTypes": [
        "major"
      ]
    },
    {
      "enabled": false,
      "matchDatasources": [
        "docker"
      ],
      "matchUpdateTypes": [
        "minor",
        "patch"
      ]
    },

[rarkins]

It's because regex versioning is being used instead of the default docker and it doesn't understand "precision"

[nitrocode]

Hi @rarkins. Thank you for the response

Is there a way I can disable the regex versioning ? I cannot seem to find the configuration that disables the default docker precisioning.

And also just wondering, since I disabled patch updates for docker (as seen above), how come that didnt disable it?

[rarkins]

Please create a minimal reproduction

[wyardley]

I am running into a similar situation with github-releases trying to update, e.g., 1.10 to 1.11.0 vs 1.11. I read this post and thought maybe setting rangeStrategy would help, but it didn't.

I've made a repro repo, and will start a new thread, since the underlying issues may be slightly different.

[wyardley]

@nitrocode not sure if helps in your case, but just in case, dropping the link here: #34541