Possible bug in PEP440

[PaulTorm]

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.

Gitlab, v39

Please tell us more about your question or problem

Renovate will not accept Final Releases <major>.<minor> as a valid PEP440 versioning scheme - contradicting to what the PEP440 documentation says.
We have tracked down the version to when it first occurred to 38.64.1. Every prior version seems to work.

In our specific case:
current version 4.25 was not validated as a correct PEP440 version - therefore no newer version was searched.

We have found two workarounds as a quick fix for us:

1. Not using final releases - use the latest patch release
2. Use python version template - "versioningTemplate": "python"

It would be great if a proper solution could be found for this problem.

Logs (if relevant)

Logs

WARN: Unexpected range error (repository=local)
       "currentValue": "4.25",
       "err": {
         "message": "Invalid pep440 currentValue",
         "stack": "TypeError: Invalid pep440 currentValue\n    at parseCurrentRange (/usr/local/renovate/lib/modules/versioning/pep440/range.ts:256:11)\n    at Object.getNewValue (/usr/local/renovate/lib/modules/versioning/pep440/range.ts:120:14)\n    at generateUpdate (/usr/local/renovate/lib/workers/repository/process/lookup/generate.ts:57:39)\n    at lookupUpdates (/usr/local/renovate/lib/workers/repository/process/lookup/index.ts:474:44)\n    at Function.wrap (/usr/local/renovate/lib/util/stats.ts:38:20)\n    at fetchDepUpdates (/usr/local/renovate/lib/workers/repository/process/fetch.ts:58:42)\n    at /usr/local/renovate/lib/workers/repository/process/fetch.ts:104:23\n    at /usr/local/renovate/node_modules/.pnpm/p-map@4.0.0/node_modules/p-map/index.js:57:22"
       }
 WARN: Unexpected range error (repository=local)
       "currentValue": "4.25",
       "err": {
         "message": "Invalid pep440 currentValue",
         "stack": "TypeError: Invalid pep440 currentValue\n    at parseCurrentRange (/usr/local/renovate/lib/modules/versioning/pep440/range.ts:256:11)\n    at Object.getNewValue (/usr/local/renovate/lib/modules/versioning/pep440/range.ts:120:14)\n    at generateUpdate (/usr/local/renovate/lib/workers/repository/process/lookup/generate.ts:57:39)\n    at lookupUpdates (/usr/local/renovate/lib/workers/repository/process/lookup/index.ts:474:44)\n    at Function.wrap (/usr/local/renovate/lib/util/stats.ts:38:20)\n    at fetchDepUpdates (/usr/local/renovate/lib/workers/repository/process/fetch.ts:58:42)\n    at /usr/local/renovate/lib/workers/repository/process/fetch.ts:104:23\n    at /usr/local/renovate/node_modules/.pnpm/p-map@4.0.0/node_modules/p-map/index.js:57:22"

[github-actions[bot]]

Hi there,

Get your discussion fixed faster 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