Bump lettuce-core from 5.2.1.RELEASE to 6.1.0.RELEASE

[dependabot]

Bumps lettuce-core from 5.2.1.RELEASE to 6.1.0.RELEASE.

Release notes

Sourced from lettuce-core's releases.

6.1.0.RELEASE

The Lettuce team is delighted to announce general availability of Lettuce 6.1.

This is a massive release thanks to all the community contributions. Most notable changes that ship with this release are:

• Support for Redis 6.2 commands and modifier/argument updates
• Micrometer integration
• CommandListeners API to intercept Redis commands
• extended Keep-Alive options
• Coroutine variant of ScanStream
• TCP NoDelay enabled by default
• Experimental support for io_uring
• Java Flight Recorder Integration for Connection and Cluster Events

Lettuce 6 supports Redis 2.6+ up to Redis 6.x. In terms of Java runtime, Lettuce requires at least Java 8 and works with Java 16.

Thanks to all contributors who made Lettuce 6.1.0 possible.

Documentation

Reference documentation: https://lettuce.io/core/6.1.0.RELEASE/reference/ Javadoc: https://lettuce.io/core/6.1.0.RELEASE/api/

Micrometer Integration

Lettuce ships an integration for Micrometer. Commands are tracked by using two Micrometer Times: lettuce.command.firstresponse and lettuce.command.completion. The following tags are attached to each timer:

• command: Name of the command (GET, SET, …)
• local: Local socket (localhost/127.0.0.1:45243 or ANY when local distinction is disabled, which is the default behavior)
• remote: Remote socket (localhost/127.0.0.1:6379)

To enable Micrometer, create MicrometerCommandLatencyRecorder from MeterRegistry and register it in ClientResources:

MeterRegistry meterRegistry = …;
MicrometerOptions options = MicrometerOptions.create();
ClientResources resources = ClientResources.builder().commandLatencyRecorder(new MicrometerCommandLatencyRecorder(meterRegistry, options)).build();
RedisClient client = RedisClient.create(resources);

Make sure to have Micrometer on your class path (example from a Maven pom.xml):

<dependency>
    <groupId>io.micrometer</groupId>
    <artifactId>micrometer-core</artifactId>
</tr></table> 

... (truncated)

Changelog

Sourced from lettuce-core's changelog.

Lettuce 6.1.0 RELEASE NOTES

The Lettuce team is delighted to announce general availability of Lettuce 6.1.

This is a massive release thanks to all the community contributions. Most notable changes that ship with this release are:

• Support for Redis 6.2 commands and modifier/argument updates
• Micrometer integration
• CommandListeners API to intercept Redis commands
• extended Keep-Alive options
• Coroutine variant of ScanStream
• TCP NoDelay enabled by default
• Experimental support for io_uring
• Java Flight Recorder Integration for Connection and Cluster Events

Lettuce 6 supports Redis 2.6+ up to Redis 6.x. In terms of Java runtime, Lettuce requires at least Java 8 and works with Java 16.

Thanks to all contributors who made Lettuce 6.1.0 possible.

If you need any support, meet Lettuce at

• GitHub Discussions: https://github.com/lettuce-io/lettuce-core/discussions
• Stack Overflow (Questions): https://stackoverflow.com/questions/tagged/lettuce
• Join the chat at https://gitter.im/lettuce-io/Lobby for general discussion
• GitHub Issues (Bug reports, feature requests): https://github.com/lettuce-io/lettuce-core/issues
• Documentation: https://lettuce.io/core/6.1.0.RELEASE/reference/
• Javadoc: https://lettuce.io/core/6.1.0.RELEASE/api/

Micrometer Integration

Lettuce ships an integration for Micrometer. Commands are tracked by using two Micrometer Times: lettuce.command.firstresponse and lettuce.command.completion. The following tags are attached to each timer:

• command: Name of the command (GET, SET, …)
• local: Local socket (localhost/127.0.0.1:45243 or ANY when local distinction is disabled, which is the default behavior)
• remote: Remote socket (localhost/127.0.0.1:6379)

To enable Micrometer, create MicrometerCommandLatencyRecorder from MeterRegistry and register it in ClientResources:

MeterRegistry meterRegistry = …;
MicrometerOptions options = MicrometerOptions.create();
ClientResources resources = ClientResources.builder().commandLatencyRecorder(new MicrometerCommandLatencyRecorder(meterRegistry, options)).build();
RedisClient client = RedisClient.create(resources);

... (truncated)

Commits

• d151952 [maven-release-plugin] prepare release 6.1.0.RELEASE
• d2f6ace Polishing #1693
• 5f118d4 Rollback to Netty 4.1.60.Final #1696
• 88b3806 Upgrade test dependencies #1693
• 8a5c990 Upgrade to Micrometer 1.6.5 #1698
• 15c197c Upgrade to Kotlin 1.4.32 #1697
• 06cbb7b Upgrade to Netty 4.1.61.Final #1696
• 286f4c7 Update release notes #1693
• 962d1a6 Ensure Kotlin 1.3 compatibility #1694
• 194b6f6 Polishing #1683
• Additional commits viewable in compare view

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 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]

Superseded by #49.