Update dependency redis.clients:jedis to v5#44
Merged
IllusionTheDev merged 1 commit into2.0from Oct 11, 2023
Merged
Conversation
27e8b22 to
73abd3b
Compare
73abd3b to
4dda977
Compare
|
Kudos, SonarCloud Quality Gate passed! |
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:
4.4.3->5.0.1⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
redis/jedis (redis.clients:jedis)
v5.0.1: 5.0.1Changes
🔥 Breaking Changes
List<KeyValue<>>for a map reply - those now returnMap<>.🚀 New Features
🧰 Maintenance
Contributors
We'd like to thank all the contributors who worked on this release!
@sazzad16
v5.0.0: 5.0.0What's New?
Automatic Cross-Cluster Failover
We're happy to introduce the Cross-Cluster Failover feature in Jedis. This feature provides high availability and resilience by allowing seamless transitions between Redis clusters during unforeseen failures or downtimes. It's a built-in tool to minimize manual intervention and downtime and ensure a more resilient application infrastructure.
Learn more about how you can automate the failover process in our documentation.
Full Redis 7.2 and RESP3 Support
Examples to enable RESP3 are included later in this release note.
Changes
🔥 Breaking Changes (Listed here)
🚀 New Features
🧪 Experimental Features
🐛 Bug Fixes
🧰 Maintenance
2023022to2023061(#3472)RESP3 Examples
This release introduces enabling RESP3 Redis connection, when the Redis server supports it.
v4.4.5: 4.4.5Changes
🚀 New Features
🧰 Maintenance
Contributors
We'd like to thank all the contributors who worked on this release!
@sazzad16
v4.4.4: 4.4.4Changes
🔥 Breaking Changes
🧰 Maintenance
pipelined()method in JedisSentineled directly returnsPipelineobject (#3517)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.