constraintsFiltering=strict in relation to poetry dependency specification #31661
-
What would you like help with?I would like help with my configuration How are you running Renovate?Mend Renovate hosted app on github.com If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.No response Please tell us more about your question or problemAfter opening #31654 and being told about I now have the following configuration
I have done some investigations related to the declaration of the python dependencies (i.e. the constraint) in the pyproject.toml With the following configuration, the python upgrade MR is correct (i.e. 3.9 => 3.11).
But, they all show a warning in the logs
In the debug logs for When using If we pin the python version to Is renovate constraint "interpreter" compatible with the poetry dependency specification or is it mandatory to pin the python constraint when using Looking at the log, it seems that it use the pep440 specification which will not match the poetry dependency specification. Logs (if relevant)Logs
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Beta Was this translation helpful? Give feedback.
To get this to work you'll need to manually set versioning=poetry like so: https://github.com/renovate-reproductions/31661/blob/29478e1b3c4c44c7085b81049457cccf11389bd4/renovate.json#L11-L14
The Poetry manager defaults to using pep440 versioning if the current version is compatible, but pep440 doesn't have a "subset()" function required for constraints filtering