Unexpected Version Upgrade Detected

[shoji-kai]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

GitHub, Renovate version: 39.176.2

Please tell us more about your question or problem

I want to keep the PostgreSQL version in my docker-compose.yaml within the range 16 <= version < 17, so I wrote the following packageRules:

{
  "matchPackageNames": ["postgres"],
  "matchCurrentVersion": ">=16",
  "allowedVersions": "<17"
}

However, with this configuration, PostgreSQL v17 is also included as an upgrade target.
I know that there are alternative ways to avoid this issue, but shouldn’t this configuration work as expected?

Logs (if relevant)

Logs

            "autoReplaceStringTemplate": "{{depName}}{{#if newValue}}:{{newValue}}{{/if}}{{#if newDigest}}@{{newDigest}}{{/if}}",
            "currentValue": "16.7-alpine3.21",
            "currentVersion": "16.7",
            "currentVersionAgeInDays": 8,
            "currentVersionTimestamp": "2025-02-16T00:08:18.328Z",
            "datasource": "docker",
            "depName": "postgres",
            "fixedVersion": "16.7-alpine3.21",
            "isSingleVersion": true,
            "lookupName": "library/postgres",
            "packageName": "postgres",
            "registryUrl": "https://index.docker.io",
            "replaceString": "postgres:16.7-alpine3.21",
            "versioning": "docker",
            "warnings": [],
            "updates": [
              {
                "bucket": "non-major",
                "newVersion": "16.8",
                "newValue": "16.8-alpine3.21",
                "releaseTimestamp": "2025-02-22T06:09:26.731Z",
                "newVersionAgeInDays": 2,
                "newMajor": 16,
                "newMinor": 8,
                "newPatch": null,
                "updateType": "minor",
                "pendingChecks": true,
                "libYears": 0.01712545671613394,
                "branchName": "renovate/non-major-updates"
              },
              {
                "bucket": "major",
                "newVersion": "17.3",
                "newValue": "17.3-alpine3.21",
                "releaseTimestamp": "2025-02-16T00:08:45.808Z",
                "newVersionAgeInDays": 8,
                "newMajor": 17,
                "newMinor": 3,
                "newPatch": null,
                "updateType": "major",
                "pendingVersions": [
                  "17.4-alpine3.21"
                ],
                "libYears": 8.713850837138508e-7,
                "branchName": "renovate/postgres-17.x"
              }

[RahulGautamSingh]

It should work. Could you please create a minimal reproduction so we can be sure there aren't any other factors leading to the unexpected behaviour?

[shoji-kai]

Thank you for your reply. I have created it. Does this look good to you?

https://github.com/shoji-kai/minimal-reproduction-template

[github-actions[bot]]

Hi there,

Please help this Discussion progress 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.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team