Pin build-time requirements versions, renovatebot will take care of the updates #8689
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Maintainer merge checklist
Component: xxx
label.api-deprecation
orapi-break
label.release-highlight
label to be highlighted in release notes.versionadded
,versionchanged
as needed.In past we left dependencies (both build-time and run-time) dependencies unpinned.
That led to CI/CD pipeline breakages (Like https://github.com/kivy/kivy/actions/runs/8765819880/job/24057222737) and users finding out something was not working as expected with newer (and untested) versions of a dependency.
By starting out with built-time dependencies, the idea is to migrate to pinned dependencies, and leave renovatebot (#8688) try out new versions and open PRs for us.