Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support range/range constraints filtering #8476

Closed
rarkins opened this issue Jan 31, 2021 · 1 comment · Fixed by #20842
Closed

Support range/range constraints filtering #8476

rarkins opened this issue Jan 31, 2021 · 1 comment · Fixed by #20842
Labels
datasource:pypi priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)

Comments

@rarkins
Copy link
Collaborator

rarkins commented Jan 31, 2021

What would you like Renovate to be able to do?

Support the scenario where both the repo and datasource have a compatibility range. e.g. the repo has python >=3.7 and the package has >=3.6.

Did you already have any implementation ideas?

You could try doing it algebraically, or practically.

Algebraic seems hard.

If it were practical, you'd use an actual datasource to identify all the possible versions (e.g. of python) and then compute matching values for both ranges before checking that the second range is a subset of the first.
@rarkins rarkins added type:feature Feature (new functionality) priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others datasource:pypi status:requirements Full requirements are not yet known, so implementation should not be started labels Jan 31, 2021
@rarkins rarkins mentioned this issue Jan 31, 2021
Closed
@todo todo bot mentioned this issue Jan 31, 2021
Merged
@rarkins rarkins changed the title Support range/range compatibility filtering Support range/range constraints filtering Feb 26, 2021
@rarkins rarkins mentioned this issue Feb 26, 2021
Closed
5 tasks
@Lctrs Lctrs mentioned this issue Feb 4, 2023
Closed
6 tasks
@Lctrs Lctrs mentioned this issue Mar 10, 2023
Merged
6 tasks
@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 35.7.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
datasource:pypi priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(datasource): support range constraints filtering
2 participants
@rarkins @renovate-release