Renovate doesn't pick up updates for new revisions Bitnami Redis docker image #29094
Replies: 3 comments 10 replies
-
|
From your point of view, do you wish to restrict the debian version or r version? Or you don't mind as long as it's debian, plus the Redis version goes up? |
Beta Was this translation helpful? Give feedback.
-
|
I don't mind both versions going up |
Beta Was this translation helpful? Give feedback.
-
|
In this case you should be able to:
Essentially this means "only the version part before |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your suggestion @rarkins! Dockerfile:
renovate.json: {
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:base"
],
"packageRules": [
{
"matchPackagePatterns": ["docker.io/bitnami/redis"],
"matchSourceUrlPrefixes": ["https://hub.docker.com/r/bitnami/redis"],
"versioning": "docker",
"versionCompatibility": "^(?<version>[^-]+)(?<compatibility>-debian-)"
}
]
}However, Renovate still isn't creating PRs to update to newer revision numbers (e.g., from I've confirmed that newer revisions exist on Docker Hub and that Renovate is running without errors. Is there anything else I might be missing in the configuration, or could there be another factor influencing this behavior? Thanks again for your help! |
Beta Was this translation helpful? Give feedback.
-
|
Both your match fields are wrong. Keep it simple and use a matchPackageNames match instead |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I've tried this config, but still no luck. I'm not so proficient with the custom match patterns, could you point out where could be a mistake in my case with this Redis image? |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
Here is the minimal repoduction repo: https://github.com/gregory-hive/renovate-redis-image-issue-minimal-reproduction |
Beta Was this translation helpful? Give feedback.
-
|
Relevant logs show it matches: The problems turns out to be: your reproduction is expecting an upgrade of the Debian12 r value, but with this approach Renovate ignores it. When I roll back to a 7.2.3 tag I can confirm you get an upgrade to 7.2.4: https://github.com/renovate-reproductions/29094/pull/1/files But also note all r values are equal so it's picked the first one r1. Unfortunately I'm not sure we have a solution for this. Another possibility could be to use regex versioning but you have five parts to this version, while we support four. |
Beta Was this translation helpful? Give feedback.
-
|
wrong, regex versioning supports five parts 😉 |
Beta Was this translation helpful? Give feedback.
-
|
try this: {
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:base"
],
"packageRules": [
{
"description": "Use custom regex versioning for bitnami images",
"matchPackagePrefixes": ["gcr.io/bitnami-containers/", "bitnami/"],
"matchDatasources": ["docker"],
"versioning": "regex:^(?<major>\\d+)\\.(?<minor>\\d+)\\.(?<patch>\\d+)(:?-(?<compatibility>.+)-(?<build>\\d+)(?:-r(?<revision>\\d+))?)?$"
},
]
} |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
And it works! After updating to the latest Renovate version I didn't even had to change my config to get a a PR from Renovate. Thank you guys for such incredibly quick release :) |
Beta Was this translation helpful? Give feedback.
-
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, version "latest"
Please tell us more about your question or problem
Hi all,
I'm facing an issue where Renovate isn't picking up updates for new revisions of the Bitnami Redis docker image when using a pinned version with a specific Debian release.
Here's what's happening:
Working Updates:
Renovate successfully detects and creates PRs for updates like:
-FROM docker.io/bitnami/redis:7.2.3-debian-11-r0
+FROM docker.io/bitnami/redis:7.2.4-debian-11-r0
Missing Updates:
However, it doesn't seem to create PRs for updates to newer revisions within the same Debian release, such as:
-FROM docker.io/bitnami/redis:7.2.4-debian-11-r0
+FROM docker.io/bitnami/redis:7.2.4-debian-11-r5
My Renovate config is as follows:
{ "$schema": "https://docs.renovatebot.com/renovate-schema.json", "extends": [ "config:base" ], "packageRules": [ { "matchPackagePatterns": ["docker.io/bitnami/redis"], "matchSourceUrlPrefixes": ["https://hub.docker.com/r/bitnami/redis"] } ] }I've tried various wildcard patterns for the version field (e.g., 7.2.4-debian-11-r*), and also loose versions + allowed versions as it was mentioned in another discussion but it doesn't seem to work.
Example of such config:
{ "$schema": "https://docs.renovatebot.com/renovate-schema.json", "extends": [ "config:base" ], "packageRules": [ { "matchPackagePatterns": ["docker.io/bitnami/redis"], "matchSourceUrlPrefixes": ["https://hub.docker.com/r/bitnami/redis"], "versioning": "loose", "allowedVersions": "^7\\.2\\.4-debian-12-r\\d+$" } ] }Is there a specific configuration or setting I'm missing to make Renovate detect these revision updates consistently? Any help or suggestions would be greatly appreciated!
Thank you!
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions