[bug?] Suggesting update for docker image (eclipse-temurin) without respecting versioning "granularity" #43634
-
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.195.0 Please tell us more about your question or problemFor a few weeks now, Renovate creates PRs to update our compose.yaml and Dockerfile from I don't understand why. It should IMO and IIUC stay on 21-jre (particularly as they do point to the same sha256! here and there), and it didn't happen with 21.0.9_10-jre for instance. We do use a Docker registry mirror, but I don't think that matters here. We're running Renovate on Jenkins using a command similar to: (there are a few other params for inherited config, and environment variables for secrets) Logs (if relevant)Logs |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
This comment was marked as low quality.
This comment was marked as low quality.
-
|
Sorry, this user is spamming the Discussions with AI generated replies. I've blocked them now @RahulGautamSingh mind taking a look at this question? |
Beta Was this translation helpful? Give feedback.
My bad, I confused the details.
The mechanism: default docker versioning won't offer 21-jre → 21.0.11_10-jre because it enforces a matching segment count. The preset overrides that with regex versioning, which has no segment-count rule, so 21.0.11 sorts above 21 and the update is offered
To stay on 21-jre today, you'll need to add a package rule that ignores updates when the current tag is major-only:
{ "matchDatasources": ["docker"], "matchPackageNames": ["eclipse-temurin"], "matchCurrentValue": "/^\\d+-/", "allowedVersions": "/^\\d+-/" }Longer term this looks like a real limitation in the preset's regex versioning and we should track fixing it. Possibly using the docker versioning coul…