Bump lettuce-core from 5.1.1.RELEASE to 5.1.6.RELEASE in /examples

[dependabot-preview]

Bumps lettuce-core from 5.1.1.RELEASE to 5.1.6.RELEASE.

Release notes

Sourced from lettuce-core's releases.

5.1.6.RELEASE

The Lettuce team is pleased to announce the Lettuce 5.1.6 service release!
This release ships bug fixes and dependency upgrades. Upgrading to the new version is recommended.

Thanks to all contributors who made Lettuce 5.1.6.RELEASE possible.

Lettuce requires a minimum of Java 8 to build and run and #RunsLikeHeaven on Java 11.
It is tested continuously against the latest Redis source-build.

Enhancements

• Improve mutators for ClientOptions, ClusterClientOptions, and ClientResources #1003

Fixes

• ClassCastException occurs when using RedisCluster with custom-command-interface and Async API #994 (Thanks to @​tamanugi)
• Application-level exceptions in Pub/Sub notifications mess up pub sub decoding state and cause timeouts #997 (Thanks to @​giridharkannan)
• RedisClient.shutdown hangs because event loops terminate before connections are closed #998 (Thanks to @​Poorva17)

Other

• Upgrade to Reactor Core 3.2.8.RELEASE #1006

Documentation

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

5.1.5.RELEASE

The Lettuce team is pleased to announce the Lettuce 5.1.5 service release!
This release ships with two critical fixes, primarily for the recently introduced reactive signal emission on non-I/O threads, so reactive single-connection systems can utilize more threads for item processing and are not limited to a single thread. The issue that is being fixed is retention of signal ordering as signals can be dispatched out of order.

Thanks to all contributors who made Lettuce 5.1.5.RELEASE possible.

Lettuce requires a minimum of Java 8 to build and run and #RunsLikeHeaven on Java 11.
It is tested continuously against the latest Redis source-build.

Fixes

• Result is lost when published on another executor #986 (Thanks to @​trueinsider)
• Cancel ClusterTopologyRefreshTask in RedisClusterClient.shutdownAsync() #989 (Thanks to @​johnsiu)

Other

• Upgrade to AssertJ 3.12.0 #983
• Upgrade to AssertJ 3.12.1 #991
• Javadoc is missing Javadoc links to Project Reactor types #942

Documentation

... (truncated)

Changelog

Sourced from lettuce-core's changelog.

Lettuce 5.1.6 RELEASE NOTES

The Lettuce team is pleased to announce the Lettuce 5.1.6 service release!
This release ships bug fixes and dependency upgrades. Upgrading to
the new version is recommended.

Thanks to all contributors who made Lettuce 5.1.6.RELEASE possible.

Lettuce requires a minimum of Java 8 to build and run and #RunsLikeHeaven on Java 11.
It is tested continuously against the latest Redis source-build.

If you need any support, meet Lettuce at

• Google Group (General discussion, announcements and releases): https://groups.google.com/d/forum/lettuce-redis-client-users
  or lettuce-redis-client-users@googlegroups.com
• 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/5.1.6.RELEASE/reference/
• Javadoc: https://lettuce.io/core/5.1.6.RELEASE/api/

Enhancements

• Improve mutators for ClientOptions, ClusterClientOptions, and ClientResources #1003

Fixes

• ClassCastException occurs when using RedisCluster with custom-command-interface and Async API #994 (Thanks to @​tamanugi)
• Application-level exceptions in Pub/Sub notifications mess up pub sub decoding state and cause timeouts #997 (Thanks to @​giridharkannan)
• RedisClient.shutdown hangs because event loops terminate before connections are closed #998 (Thanks to @​Poorva17)

Other

• Upgrade to Reactor Core 3.2.8.RELEASE #1006

Commits

• 143da7d [maven-release-plugin] prepare release 5.1.6.RELEASE
• ed17478 Update changelog #1007
• 254b6f0 Upgrade to Reactor Core 3.2.8.RELEASE #1006
• 3381ecd Improve mutators for ClientOptions, ClusterClientOptions, and ClientResources...
• 54a2912 Guard Pub/Sub callbacks against exceptions #997
• d30ce30 Polishing #998
• 881d0ed Synchronize ClientResources shutdown with channel close completion #998
• 64de81b Return AsyncCommand object in AsyncExecutableCommand execution #994
• 4e4fdf4 [maven-release-plugin] prepare for next development iteration
• de61c62 [maven-release-plugin] prepare release 5.1.5.RELEASE
• 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.

If all status checks pass Dependabot will automatically merge this pull request.

---

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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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 badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.