dependabot[bot] opened a new pull request, #20680: URL: https://github.com/apache/druid/pull/20680
Bumps [redis.clients:jedis](https://github.com/redis/jedis) from 7.0.0 to 8.0.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/redis/jedis/releases";>redis.clients:jedis's releases</a>.</em></p> <blockquote> <h2>8.0.2</h2> <p><strong>Jedis 8.0.2</strong> is a maintenance release for the 8.0 line, fixing <code>MultiDbClient</code> failover so it recovers to a healed database and keeps health checks running when no failover candidate is available.</p> <h1>Changes</h1> <h2>๐ Bug Fixes</h2> <ul> <li>Fail over to a recovered database when the active one is inoperable (<a href="https://redirect.github.com/redis/jedis/issues/4774";>#4774</a>)</li> <li>Keep MultiDbClient health checks alive when failover has no candidate (<a href="https://redirect.github.com/redis/jedis/issues/4759";>#4759</a>)</li> </ul> <h2>๐งฐ Maintenance</h2> <ul> <li>Document that automatic recovery is not guaranteed after the permanent failure (<a href="https://redirect.github.com/redis/jedis/issues/4776";>#4776</a>)</li> <li>Update failover.md and some javadoc (<a href="https://redirect.github.com/redis/jedis/issues/4772";>#4772</a>)</li> </ul> <h2>Contributors</h2> <p>We'd like to thank all the contributors who worked on this release!</p> <p><a href="https://github.com/ggivo";><code>@โggivo</code></a></p> <p><strong>Full Changelog</strong>: <a href="https://github.com/redis/jedis/compare/v8.0.1...v8.0.2";>https://github.com/redis/jedis/compare/v8.0.1...v8.0.2</a></p> <h2>8.0.1</h2> <p><strong>Jedis 8.0.1</strong> is a maintenance release for the 8.0 line, fixing stale cluster topology after failover in <code>JedisCluster</code>.</p> <h1>Changes</h1> <h2>๐ Bug Fixes</h2> <ul> <li>Refresh primaryNodesCache in JedisClusterInfoCache.discoverClusterSlots (<a href="https://redirect.github.com/redis/jedis/issues/4692";>#4692</a>, backported in <a href="https://redirect.github.com/redis/jedis/issues/4694";>#4694</a>)</li> </ul> <h2>Contributors</h2> <p>We'd like to thank all the contributors who worked on this release!</p> <p><a href="https://github.com/insaf021";><code>@โinsaf021</code></a></p> <p><strong>Full Changelog</strong>: <a href="https://github.com/redis/jedis/compare/v8.0.0...v8.0.1";>https://github.com/redis/jedis/compare/v8.0.0...v8.0.1</a></p> <h2>8.0.0</h2> <p><strong>Jedis 8.0.0</strong> completes the client class consolidation started in 7.0.0, modernizes protocol defaults, tightens security defaults, and adds command coverage for Redis 8.8 and the Redis 8.10 preview.</p> <ul> <li><strong>RESP3 auto-negotiation</strong> on by default for all UnifiedJedis-based clients (with graceful RESP2 fallback)</li> <li><strong>Final removal of legacy JedisPooled / JedisSentineled</strong> classes in favor of the RedisClient family introduced in 7.0.0</li> <li><strong>Removal of deprecated UnifiedJedis public constructors</strong></li> <li><strong>Internal refactoring</strong> that affects users of low-level extension points (custom CommandExecutor, Transaction subclasses, ClusterPipeline, CommandObjects) โ protocol and connection wiring is now explicit at construction time</li> <li><strong>Search modernization</strong> โ the low-level cursor APIs are superseded by ftAggregateIterator(), and the manual broadcast API is removed (Redis 8.0+ broadcasts FT.CREATE server-side)</li> <li><strong>TLS hostname verification enforced</strong> by default in DefaultJedisSocketFactory</li> <li><strong>New Redis 8.8 command coverage</strong> โ XNACK, JSON.SET FPHA, Array commands, INCREX, COUNT aggregator on ZINTER / ZUNION(STORE) and their *STORE variants, multi-aggregator TS.RANGE / TS.MRANGE, plus an experimental COLLECT parameter for FT.AGGREGATE</li> <li><strong>Redis 8.10 command coverage</strong> โ HIMPORT (Hinted Hash Templates), FT.ALIASLIST, MAXCOUNT / MAXSIZE on XREAD and XREADGROUP, SUNIONCARD / SDIFFCARD, LMOVEM / BLMOVEM, TS.READ, TS.NRANGE / TS.NREVRANGE, TS.QUERYLABELS, and EXCLUDEEMPTY on TS.MRANGE / TS.MREVRANGE</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/redis/jedis/blob/master/docs/release-process.md";>redis.clients:jedis's changelog</a>.</em></p> <blockquote> <h1>Release Process</h1> <p>Releases are drafted automatically by <a href="https://github.com/redis/jedis/blob/master/.github/workflows/release-drafter.yml";>Release Drafter</a> and deployed by the <a href="https://github.com/redis/jedis/blob/master/.github/workflows/version-and-release.yml";>Release workflow</a> when a draft is published.</p> <h2>Branches</h2> <table> <thead> <tr> <th>Branch</th> <th>Hosts</th> <th>Example</th> </tr> </thead> <tbody> <tr> <td><code>master</code></td> <td>next minor or major</td> <td><code>8.1.0-SNAPSHOT</code></td> </tr> <tr> <td><code>MAJOR.x</code></td> <td><code>MAJOR.0.PATCH</code></td> <td><code>7.x</code>, <code>8.x</code></td> </tr> <tr> <td><code>MAJOR.MINOR.x</code></td> <td><code>MAJOR.MINOR.PATCH</code></td> <td><code>7.5.x</code>, <code>8.1.x</code></td> </tr> </tbody> </table> <ul> <li>Minor and major releases, including betas, are tagged on <code>master</code>.</li> <li>Patch releases are tagged on their maintenance branch, never on <code>master</code>.</li> <li>A maintenance branch is cut from the GA tag commit (<code>8.1.x</code> from <code>v8.1.0</code>).</li> <li>Fixes land on <code>master</code> first and are backported with a PR titled <code>Backport #<pr> to <line>: <original title></code>, carrying the original labels.</li> </ul> <h2>How the draft is produced</h2> <p>On every push to <code>master</code> or a maintenance branch, Release Drafter updates one draft per branch:</p> <ul> <li><strong>Version</strong> is derived from the nearest GA tag reachable from the branch, ignoring prerelease tags: patch bump on maintenance branches, minor bump on <code>master</code>. Example: <code>8.x</code> at <code>v8.0.1</code> drafts <code>8.0.2</code>; <code>master</code> at <code>v8.0.0</code> drafts <code>8.1.0</code>.</li> <li><strong>Changes</strong> are the pull requests merged to the branch since the latest GA release published from that branch. For the first patch after a branch is cut, the GA tag's commit date is used as the cutoff instead.</li> <li>Betas are prereleases and are not used as a base, so GA notes are cumulative since the previous GA.</li> <li>PRs labeled <code>skip-changelog</code> or <code>churn</code> are excluded. Unlabeled PRs appear uncategorized, so label backports.</li> </ul> <h2>Publishing</h2> <ol> <li>Review the draft on the Releases page and edit the notes if needed.</li> <li>Publish from the draft. This keeps the release target on the right branch, which the next draft on that branch depends on. Do not create releases from the tag page.</li> <li>For a patch of an older line, untick <strong>Set as the latest release</strong>.</li> <li>Publishing creates the tag and triggers the Release workflow, which sets the Maven version from the tag and deploys to Maven Central.</li> </ol> <p>Major releases and betas are not derived automatically. Run the workflow</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/redis/jedis/commit/eb8cd653e0400f30337e6cd927459d995cd8f5ba";><code>eb8cd65</code></a> Backport <a href="https://redirect.github.com/redis/jedis/issues/4777";>#4777</a> to 8.0.x: Draft releases from maintenance branches (<a href="https://redirect.github.com/redis/jedis/issues/4778";>#4778</a>)</li> <li><a href="https://github.com/redis/jedis/commit/d18e2568f9ed208dec8bfe55e4dda36c96d05e0b";><code>d18e256</code></a> Backport <a href="https://redirect.github.com/redis/jedis/issues/4771";>#4771</a> to 8.0.x: Document that automatic recovery is not guaranteed a...</li> <li><a href="https://github.com/redis/jedis/commit/53fecac3eac0f394ab7bf332a7bb5ae2e87a0fdd";><code>53fecac</code></a> Backport <a href="https://redirect.github.com/redis/jedis/issues/4765";>#4765</a> to 8.0.x: Fail over to a recovered database when the active on...</li> <li><a href="https://github.com/redis/jedis/commit/b7f50673f7e482fd1d0000f72a2e60fbe25cadf1";><code>b7f5067</code></a> Backport <a href="https://redirect.github.com/redis/jedis/issues/4745";>#4745</a> to 8.0.x: Update failover.md and some javadoc (<a href="https://redirect.github.com/redis/jedis/issues/4772";>#4772</a>)</li> <li><a href="https://github.com/redis/jedis/commit/af815c5c1d159b44dc350538eff5ca957959a570";><code>af815c5</code></a> Backport <a href="https://redirect.github.com/redis/jedis/issues/4756";>#4756</a> to 8.0.x: Keep MultiDbClient health checks alive when failover...</li> <li><a href="https://github.com/redis/jedis/commit/96450d3b6dbf95b23b1a56f619a6ddf99e68f240";><code>96450d3</code></a> Bump snapshot version to 8.0.2 (<a href="https://redirect.github.com/redis/jedis/issues/4715";>#4715</a>)</li> <li><a href="https://github.com/redis/jedis/commit/50ec1c87f1e96afed9d48eb5a8f9c62f7cad55c6";><code>50ec1c8</code></a> Backport <a href="https://redirect.github.com/redis/jedis/issues/4692";>#4692</a> to 8.0.x: refresh primaryNodesCache in JedisClusterInfoCache.d...</li> <li><a href="https://github.com/redis/jedis/commit/36135a030dba1007ab1de9bb254397c580114b07";><code>36135a0</code></a> Point snapshot example at 8.0.1-SNAPSHOT on the 8.x branch</li> <li><a href="https://github.com/redis/jedis/commit/2de1a6d05b843fe6f00c408c1af1b8a850f9bbad";><code>2de1a6d</code></a> List Redis 8.6, 8.8 and 8.10 as supported in README</li> <li><a href="https://github.com/redis/jedis/commit/fcf59cdc59fa080e82ad7e24a64eed2bc15a2cbc";><code>fcf59cd</code></a> Update version references in README and docs for 8.0.0</li> <li>Additional commits viewable in <a href="https://github.com/redis/jedis/compare/v7.0.0...v8.0.2";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 show <dependency name> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
