fix(deps): update python dependencies (major) [python] (major) - #4497
Open
renovate[bot] wants to merge 2 commits into
Open
fix(deps): update python dependencies (major) [python] (major)#4497renovate[bot] wants to merge 2 commits into
renovate[bot] wants to merge 2 commits into
Conversation
manast
previously approved these changes
Aug 4, 2026
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Copilot stopped work on behalf of
manast due to an error
August 4, 2026 09:48
manast
force-pushed
the
renovate/major-python-major
branch
from
August 4, 2026 10:21
b6bf16c to
0b8bd10
Compare
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.
This PR contains the following updates:
==2.0.7→==6.2.4==7.4.1→==8.1.0Release Notes
pallets-eco/croniter (croniter)
v6.2.4Compare Source
Bugfixes
fd13d2e, #240;5cd2e46, #238]v6.2.3Compare Source
Features and Improvements
W(nearest weekday) in the day-of-month field. [c79d88a]precision_in_secondsparameter tomatch()andmatch_range()to allow overriding the default matching precision. [7415d1e, #58]strictparameter tois_valid()andexpand()for cross-field validation of impossible day/month combinations. [0352d48, #199]Bugfixes
day_orandimplement_cron_bugparameters for day-of-month/day-of-week interaction. [289bf73, #75]precision_in_secondsparameter and default precision behavior formatch(). [7415d1e, #58]v6.2.2Compare Source
Packaging
License :: OSI Approved :: MIT Licenseclassifier. [270cbbc, @cdheiser]v6.2.1Compare Source
v6.2.0Compare Source
Features and Improvements
day_orandimplement_cron_bugparameters for day-of-month/day-of-week interaction. [289bf73, #75]precision_in_secondsparameter and default precision behavior formatch(). [7415d1e, #58]v6.1.0Compare Source
Features and Improvements
871e391, Benjamin Drung (@bdrung)]2d72258, Benjamin Drung (@bdrung)]1dd3562, Benjamin Drung (@bdrung)]Other
v6.0.0Compare Source
v5.0.1Compare Source
v4.0.0Compare Source
v3.0.4Compare Source
v3.0.3Compare Source
v3.0.2Compare Source
v3.0.1Compare Source
v3.0.0Compare Source
redis/redis-py (redis)
v8.1.0: 8.1.0Compare Source
Changes
✨ Highlights
Async maintenance notifications
redis-py now supports server-pushed maintenance notifications in the asyncio stack for both
standalone and cluster clients, bringing the async client to parity with the sync implementation.
When a Redis deployment signals maintenance events (such as node migration or failover windows), the
async client reacts through the maintenance-notifications handler (
redis/maint_notifications.pyandits async integration under
redis/asyncio/), allowing applications to adapt connection handlingduring maintenance without downtime. (#4177)
Expanded command coverage
This release adds a batch of new command surfaces across core data types and modules:
LMOVEM/BLMOVEMfor moving multiple elements between lists (#4174).SDIFFCARDandSUNIONCARDcardinality commands (#4171).MAXCOUNT/MAXSIZEoptions forXREADandXREADGROUP(#4173).TS.READ(#4170),TS.QUERYLABELS(#4197),TS.NRANGE/TS.NREVRANGE(#4163),and an
exclude_empty(EXCLUDEEMPTY) option forTS.MRANGE/TS.MREVRANGE(#4188).FT.ALIASLIST(#4198) and aCOLLECTreducer for aggregations (#4179).🚀 New Features
The feature considered unstable and public API might be changed in the future minor version
🐛 Bug Fixes
🧰 Maintenance
We'd like to thank all the contributors who worked on this release!
@LOGESHWAR123 @kiryazovi-redis @Stunned1 @eeshsaxena @sean-kim05 @Brumbelow @Sanjays2402 @nazarli-shabnam @chuenchen309 @petyaslavova
v8.0.1: 8.0.1Compare Source
Changes
🐛 Bug Fixes
🧰 Maintenance
We'd like to thank all the contributors who worked on this release!
@violuke @mokashang @arpitjain099 @coredumperror @elena-kolevska @vladvildanov @petyaslavova
v8.0.0: 8.0.0Compare Source
Changes
🚀 Highlights
Async Cluster PubSub
This release introduces full asyncio Cluster PubSub support, bringing shard-channel capabilities (
SSUBSCRIBE,SUNSUBSCRIBE,SPUBLISH) to the asyncRedisClusterclient. The newClusterPubSubclass inredis.asyncio.clusterautomatically routes shard-channel subscriptions to the correct cluster node based on key-slot hashing, manages per-node PubSub connections, and supports round-robin message retrieval across nodes. Users can create a cluster pubsub instance viaRedisCluster.pubsub()and usessubscribe(),sunsubscribe(), andget_sharded_message()just as they would with the sync cluster client.Keyspace and subkey notifications
Redis Keyspace Notifications are now supported for standalone and cluster deployments in both sync and async modes. New classes —
KeyspaceNotifications,ClusterKeyspaceNotifications,AsyncKeyspaceNotifications, andAsyncClusterKeyspaceNotifications— provide a high-level API for keyspace/keyevent subscriptions and subkey notification families:subkeyspace,subkeyevent,subkeyspaceitem, andsubkeyspaceevent. Convenience methods likesubscribe_keyspace(),subscribe_keyevent(),subscribe_subkeyspace(),subscribe_subkeyevent(),subscribe_subkeyspaceitem(), andsubscribe_subkeyspaceevent()simplify common patterns, with channel classes for both key and subkey channels.In cluster mode, subscriptions are managed across primary nodes because each node emits notifications only for keys it owns, with built-in topology-change handling. Sync
run_in_thread()and asynclisten()workflows are supported.Redis Array commands(https://redis.io/docs/latest/develop/data-types/arrays/)
redis-py now supports Redis Arrays, a preview Redis data type for sparse, index-addressable sequences of strings. New
AR*command helpers cover indexed reads/writes, range scans, deletion, cursor-based insertion, ring-buffer writes, metadata, text search, and aggregation, includingARGET,ARSET,ARMGET,ARMSET,ARSCAN,ARGREP,ARRING, andAROP.Type Hints Improvements (breaking changes)
The
@overloadpattern has been applied systematically across core commands (core.py), VectorSet commands, and module commands (Search, JSON, TimeSeries, Bloom filters) to provide distinct return types for sync and async clients. Previously, methods returned a combinedResponseT(i.e.,Union[Awaitable[Any], Any]), which caused static analysis tools like mypy and Pyright to flag false positives. Now, sync clients see concrete return types (e.g.,int,bool,list[str]) while async clients seeAwaitable[...]wrappers. This is a breaking change for type-checking only—runtime behavior is unchanged, but code relying on the old union return types in type annotations may need updates. Two new protocol types,SyncClientProtocolandAsyncClientProtocol, are used in overload signatures to enable this distinction.RESP3 by default with opt-in unified responses
redis-py 8.0.0 now uses RESP3 on the wire by default while preserving legacy RESP2-compatible Python response shapes for existing applications (#4052). Protocol-independent unified response shapes are available by setting
legacy_responses=False, so affected commands return the same Python structure with RESP2 or RESP3.Use
protocol=2to force RESP2 on the wire,protocol=3to opt into native RESP3 response shapes, orlegacy_responses=Falseto migrate to unified responses. Seedocs/unified_responses.rstandspecs/unified_responses_migration_guide.mdfor the affected commands and migration details.Connection and retry defaults
Default connection settings were updated:
socket_timeoutandsocket_connect_timeoutnow default to 5 seconds, TCP keepalive is enabled by default, socket reads use a 32 KB buffer, connection pools default tomax_connections=100, and retry defaults now use 10 attempts with exponential jitter backoff.Note:
socket_timeoutcan affect blocking commands such asBLPOP/BRPOP; if a command blocks longer than the client socket timeout, it may raiseTimeoutErrorbefore the command timeout elapses (#2807).🧪 Experimental Features
🚀 New Features
🔥 Breaking changes
🐛 Bug Fixes
🧰 Maintenance
We'd like to thank all the contributors who worked on this release!
@hydroblaze @Br1an67 @mokashang @swoutch @armorbreak001 @Brumbelow @paoloredis @Pack-Yak1 @abersheeran @alisaifee @majiayu000 @uglide @dmaier-redislabs @vladvildanov @petyaslavova
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.