[dependabot]

Bumps redis.clients:jedis from 8.0.1 to 8.0.2.

Release notes

Sourced from redis.clients:jedis's releases.

8.0.2

Jedis 8.0.2 is a maintenance release for the 8.0 line, fixing MultiDbClient failover so it recovers to a healed database and keeps health checks running when no failover candidate is available.

Changes

🐛 Bug Fixes

• Fail over to a recovered database when the active one is inoperable (#4774)
• Keep MultiDbClient health checks alive when failover has no candidate (#4759)

🧰 Maintenance

• Document that automatic recovery is not guaranteed after the permanent failure (#4776)
• Update failover.md and some javadoc (#4772)

Contributors

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

@​ggivo

Full Changelog: redis/jedis@v8.0.1...v8.0.2

Changelog

Sourced from redis.clients:jedis's changelog.

Release Process

Releases are drafted automatically by Release Drafter and deployed by the Release workflow when a draft is published.

Branches

Branch	Hosts	Example
master	next minor or major	8.1.0-SNAPSHOT
MAJOR.x	MAJOR.0.PATCH	7.x, 8.x
MAJOR.MINOR.x	MAJOR.MINOR.PATCH	7.5.x, 8.1.x

• Minor and major releases, including betas, are tagged on master.
• Patch releases are tagged on their maintenance branch, never on master.
• A maintenance branch is cut from the GA tag commit (8.1.x from v8.1.0).
• Fixes land on master first and are backported with a PR titled Backport #<pr> to <line>: <original title>, carrying the original labels.

How the draft is produced

On every push to master or a maintenance branch, Release Drafter updates one draft per branch:

• Version is derived from the nearest GA tag reachable from the branch, ignoring prerelease tags: patch bump on maintenance branches, minor bump on master. Example: 8.x at v8.0.1 drafts 8.0.2; master at v8.0.0 drafts 8.1.0.
• Changes 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.
• Betas are prereleases and are not used as a base, so GA notes are cumulative since the previous GA.
• PRs labeled skip-changelog or churn are excluded. Unlabeled PRs appear uncategorized, so label backports.

Publishing

1. Review the draft on the Releases page and edit the notes if needed.
2. 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.
3. For a patch of an older line, untick Set as the latest release.
4. Publishing creates the tag and triggers the Release workflow, which sets the Maven version from the tag and deploys to Maven Central.

Major releases and betas are not derived automatically. Run the workflow

... (truncated)

Commits

• eb8cd65 Backport #4777 to 8.0.x: Draft releases from maintenance branches (#4778)
• d18e256 Backport #4771 to 8.0.x: Document that automatic recovery is not guaranteed a...
• 53fecac Backport #4765 to 8.0.x: Fail over to a recovered database when the active on...
• b7f5067 Backport #4745 to 8.0.x: Update failover.md and some javadoc (#4772)
• af815c5 Backport #4756 to 8.0.x: Keep MultiDbClient health checks alive when failover...
• 96450d3 Bump snapshot version to 8.0.2 (#4715)
• See full diff in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
redis.clients:jedis	[>= 6.a0, < 7]