AndyReckt / Holiday

This is an old free Server Core i made, there is no more support for this plugin but feel free to fork or open issues/pr, i may read them!
GNU General Public License v3.0
34 stars 7 forks source link

Bump redis.clients:jedis from 4.4.3 to 5.0.2 in /shared #109

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 1 year ago

Bumps redis.clients:jedis from 4.4.3 to 5.0.2.

Release notes

Sourced from redis.clients:jedis's releases.

5.0.2

Changes

πŸ› Bug Fixes

  • Fix SORTABLE argument when creating a Search index using FT.CREATE (#3584)
  • Fix binary variants of XRANGE and XREAD commands (#3571)

πŸš€ New Features

  • Added broadcast support for FUNCTION LOAD methods (#3557)
  • Support GEOSHAPE field type in RediSearch (#3561)

🧰 Maintenance

  • Bump org.json:json from 20230618 to 20231013 (#3586)
  • Move pom.properties file into redis.clients.jedis package (#3589)
  • Warning about JedisMetaInfo movement (#3591)
  • Allow getting schema field name (#3576)

5.0.1

Changes

πŸ”₯ Breaking Changes

  • Encode map in encoded object (#3555)
    • In the 5.0.0 release, the encoded/String variants of scripting methods return List<KeyValue<>> for a map reply - those now return Map<>.

πŸš€ New Features

  • Extend CLIENT SETINFO support with added suffix rules (#3509, #3536)
  • Added quote escaping helper functions for search queries (#3544)

🧰 Maintenance

  • Re-enabled FT.DROPINDEX and FT.ALTER in pipeline (#3549)
  • Added JavaDoc for GeoRadiusResponse (#3542)

Contributors

We'd like to thank all the contributors who worked on this release!

@​sazzad16

5.0.0

What'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.

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 11 months ago

Superseded by #124.