Merged
Conversation
🛡️ Jit Security Scan Results✅ No security findings were detected in this PR
Security scan by Jit
|
rbs333
approved these changes
Mar 6, 2026
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
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
redisdependency upper bound from<7.2to<8.0uv.lockto match the new constraintCloses #527
Validation
uv lockuv run pytest(local environment has existing unrelated integration/import failures)Note
Low Risk
Low risk dependency constraint change; main risk is incompatibility with
redis7.x API/behavior if consumers upgrade without corresponding test coverage.Overview
Relaxes dependency constraints by widening the
redisrequirement from<7.2to<8.0inpyproject.toml.Lockfile updated (
uv.lock) to reflect the newredisversion range.Written by Cursor Bugbot for commit ceaa178. This will update automatically on new commits. Configure here.