Bump required-python to major.minor and .python-version to major.minor.patch

[Wesztman]

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.

Npx azure pipelines

Please tell us more about your question or problem

Hi there, I have a UV python project, when I run renovate with default config it tries to update .python-version from 3.10 to 3.13 and the requires-python from >=3.10 to >=3.13.7

I would like it to be the other way around, for requires-python to be the loose version and .python-version to be the exact one.

So instead I would like requires-python to be updated to >=3.13 and .python-version to be set to 3.13.7

I've spent the whole day trying to get this to work, but I can't seem to get it.

Is it possible and does anyone know how to configure this?

Cheers
Carl

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[GideonBear]

Hey, I had the requires-python problem too and stumbled upon a solution:

{
    packageRules: [
        {
            matchDepTypes: [
                "requires-python",
            ],
            rangeStrategy: "bump",
            extractVersion: "^(?<version>\\d+\\.\\d+)",
        },
    ],
}

As for .python-version pinning, I've tested it, and you can do that by simply changing the .python-version file to a x.y.z version. E.g. 3.14 will not be updated, but 3.14.0 will be updated to 3.14.2. Alternatively, you can change the versioning (which is docker by default) to something else (I think python or semantic should work).

Hope this helps you or someone else!

[Wesztman]

Ohh interesting, I will try it out, thanks for sharing 😁