WARN: Unexpected downgrade detected: skipping

TL;DR

It appears to be isolated to docker versioning, which is used for the docker datasource and also for github actions.

The error, verbatim

WARN: Unexpected downgrade detected: skipping { "packageName": "ghcr.io/renovatebot/renovate" "currentValue": "37.440.0" "compareValue": "37.440.0" "currentVersion": "37.440.0" "update": { "bucket": "latest", "newVersion": "37.49.0", "newValue": "37.49.0", "newMajor": 37, "newMinor": 49, "newPatch": 0, "updateType": "patch" } "allVersionsLength": 5787 "filteredReleaseVersions": [ "37.49.0" ] }

Fix

[maintainer viceice]: Saw it on our helm chart repo for renovate image `` WARN: Unexpected downgrade detected: skipping { "packageName": "ghcr.io/renovatebot/renovate" "currentValue": "37.440.0" "compareValue": "37.440.0" "currentVersion": "37.440.0" "update": { "bucket": "latest", "newVersion": "37.49.0", "newValue": "37.49.0", "newMajor": 37, "newMinor": 49, "newPatch": 0, "updateType": "patch" } "allVersionsLength": 5787 "filteredReleaseVersions": [ "37.49.0" ] } `` https://developer.mend.io/github/renovatebot/helm-charts/-/job/c23bc731-28f2-4222-89b3-4a44a521c064

Context: Issue renovatebot/renovate#29919 (closed, 41 comments): ### Describe the proposed change(s). Renovate in some cases is creating PRs to update dependencies where it's actually a downgrade. It appears to be isolated to docker versioning, which is used for the docker datasource and also for github actions. Discussion: #29901 Unfortunately we are not yet able to reproduce it Update: we have added code to suppress such workarounds and log a message WARN: Unexpected downgrade detected: skipping instead, so I have updated the title of this Issue to match

Matched source

Source: Published skill Original query: "WARN: Unexpected downgrade detected: skipping" Key terms: detected, downgrade, skipping, unexpected, warn

When to use this

• Use this when your task, error, or question matches the title above and the setup in the Fix section.

When not to use this

• Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.