pre-commit manager "suddenly" proposes old tags

[morremeyer]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

44.134.1

Please tell us more about your question or problem

2026-10-01, at 18:56 UTC, renovate opened community-tooling/charts#1471. This proposes an update to a seven year old tag, see https://github.com/norwoodj/helm-docs/tags?after=v0.1.1, instead of the newest release.

While the versioning itself looks correct here, the behavior around this changed, since renovate has been renovating this repository for years and never yet proposed this syntactically correct, yet semantically incorrect update.

Logs (if relevant)

Relevant dependency extraction excerpt

Logs

{
  "baseBranch": "main",
  "config": {
    "pre-commit": [
      {
        "deps": [
          {
            "currentValue": "v1.14.2",
            "currentVersion": "v1.14.2",
            "currentVersionAgeInDays": 819,
            "currentVersionTimestamp": "2024-07-08T10:15:33.000Z",
            "datasource": "github-tags",
            "depName": "norwoodj/helm-docs",
            "depType": "repository",
            "fixedVersion": "v1.14.2",
            "isSingleVersion": true,
            "packageName": "norwoodj/helm-docs",
            "registryUrl": "https://github.com",
            "sourceUrl": "https://github.com/norwoodj/helm-docs",
            "versioning": "semver-coerced",
            "warnings": [],
            "updates": [
              {
                "bucket": "major",
                "newVersion": "19.0614",
                "newValue": "19.0614",
                "releaseTimestamp": "2019-06-14T21:06:21.000Z",
                "newVersionAgeInDays": 2670,
                "newMajor": 19,
                "newMinor": 614,
                "newPatch": 0,
                "updateType": "major",
                "isBreaking": true,
                "branchName": "renovate/norwoodj-helm-docs-19.x"
              }
            ]
          }
        ],
        "packageFile": ".pre-commit-config.yaml"
      }
    ]
  }
}

[viceice]

it likely a side effect of

• fix(workers/lookup): only flag downgrades when the versioning orders the values #46725

renovate suggests that update because 19.0614 is greater than v1.14.2 beause it's falling back to semver-coerced

[morremeyer]

Would you consider the side-effect intentional or unintentional, e.g. is this a bug or just a side effect that will stay?

[viceice]

probably stay, I don't see how renovate should know the wrong update. you can easily workaround with a config change. I think it can be added to renovate workarounds preset

[morremeyer]

Sounds like a plan, I’ll open a PR these days

[morremeyer]

PR is open: #46838