Debian tag updated from forky-20260623 to 14 #45189
Unanswered
benbz
asked this question in
Request Help
Replies: 2 comments
This comment was marked as low quality.
This comment was marked as low quality.
|
I can also confirm I am running into this same issue, currently it keeps trying to update from "trixie-20260824" to "13", which is unwanted as I prefer having the explicit dated tag with the name inside of that specific application. I found the same as the above user where it seems to be the inverse of #42443, currently have not been able to find a workaround to it, besides doing what the above user suggested and just manually pinning it. I am running 44.39.2, on a selfhosted Forgejo Instance with the "Action" runner. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
How are you running Renovate?
Self-hosted Renovate CLI
Which platform you running Renovate on?
GitLab (.com or self-hosted)
Which version of Renovate are you using?
44.17.0
Please tell us more about your question or problem
Recent Renovate versions are attempting to upgrade Docker tag that is formatted as a dated Debian codename to an un-dated version number tag. Worse for
forky(Debian 14 / current testing), there is no un-dated version number tag.This appears to be the inverse of #42443 which was solved by #44335. I suspect that that fix is the cause of my problem and it is causing Renovate to always drop the date & convert to a version number rather than maintaining the current format of the tag.
Logs (if relevant)
Logs
All reactions