build(deps): bump django-filter upper bound to <26#52
Merged
Conversation
Raise the version ceiling from <25 to <26 so the resolver can pull in django-filter 25.1. Version 25.2 is excluded automatically because it requires Django >= 5.2 while this project pins Django 5.1. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Raise the
django-filterversion ceiling from<25to<26, allowing the resolver to upgrade from 24.3 to 25.1.Changes Made
backend/pyproject.toml:"django-filter>=24.3,<25"→"django-filter>=24.3,<26"backend/uv.lock— django-filter resolved to 25.1Notes
SplitConfigFilter,EvaluationConfigFilter,TaskLogFilter) and 12filterset_fieldsusages are unaffectedTesting
uv run pytestpasses (failures are pre-existing Redis connectivity issues unrelated to this change)Closes #23