Strict constraint filtering errors on poetry project #28615
Unanswered
daanknoope
asked this question in
Request Help
Replies: 1 comment 4 replies
-
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. To get started, please read our guide on creating a minimal reproduction. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I think I found a bug
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 problem
I'm developing a Python project with poetry as package manager and using renovate to update my dependencies. The project I'm developing should support all currently maintained Python versions. Some of my dependencies have dropped support for older versions of Python which are still activate (for example v3.8). This means that I do not want to update certain dependencies beyond the latest version which still supports the older python version.
The default behaviour of renovate seems to be to suggest updates for these packages, even if it means dropping support for older versions of Python. Since I do not want to apply changes that will drop support for older Python versions, I want to configure renovate to avoid suggesting these changes. To achieve this, I have enabled the
strict
option forconstraintsFiltering
.If I understand the docs correctly, renovate will retrieve the
python>=3.8
from my poetry config (I have verified this works) and use this as a constraint on all packages. However, when I run renovate with this configuration, it throws an error (Cannot destructure property 'epoch' of 'input' as it is null."
) and skips any suggestions for the package due to the internal error.This seems to be a bug to me, although I might have misinterpreted the docs. Could you help me figure out the problem in this situation?
This is my renovate.json:
And my sample pypoetry.toml:
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions