Bump hazelcast from 4.2.1 to 5.1.4

[dependabot]

Bumps hazelcast from 4.2.1 to 5.1.4.

Release notes

Sourced from hazelcast's releases.

v5.1.4

This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast Platform 5.1.4 release. The numbers in the square brackets refer to the issues in Hazelcast's GitHub repositories.

== Enhancements

• Removed the hazelcast-jet-cdc-mysql module from the Hazelcast Platform Enterprise distributions due to licensing. You need to manually download this module if you have the Enterprise edition. See xref:pipelines:cdc.adoc#step-4-start-hazelcast[Capture Changes from MySQL] for details. #5312
• The Kubernetes discovery plugin has been enhanced to support the service token expiration. The token is time-bound and its content is refreshed periodically in the recent Kubernetes versions. A new token reader has been implemented to get the token value periodically. #22394
• You can now provide comma-separated lists to give multiple labels for the Kubernetes Discovery Plugin configurations service-label-name, service-label-value, pod-label-name, and pod-label-value. #22401

v5.1.3

This document lists the new features, enhancements, fixed issues, and removed or deprecated features for Hazelcast Platform 5.1.3 release. The numbers in the square brackets refer to the issues in Hazelcast's GitHub repositories.

==== 5.1.3 Release Notes ====

1. Enhancements

• Improved connection handling. hazelcast/hazelcast#21641

2. Fixes

• When the hazelcast.socket.buffer.direct property is enabled, clusters no longer throw exceptions in response to text protocols such as the REST API. hazelcast/hazelcast#21700

v5.1.2

This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast 5.1.2 release. The numbers in the square brackets refer to the issues in Hazelcast's GitHub repositories.

Fixes

• Fixed an issue where a cluster could not be formed when security is enabled, various client permissions are set, and multiple members are started simultaneously. #21510
• Fixed an issue where a cluster was unresponsive when you perform a health check to see the members are in the safe state; cluster members were hanging in the REPLICA_NOT_SYNC state during such health checks. #21208
• Fixed an issue where the list of members in the cluster was reset to an empty list when the UUID of a cluster changes after its restart: this was causing startup failures since Hazelcast could not manage the events due to the empty member list after a restart. #21178
• Fixed an issue where the statistics like puts and removals were not increasing when these operations are executed through Transactional interface. #21107
• Fixed a data race in SingleProtocolEncoder; while one method of this interface is called from the input thread, another one is called from the output thread which was causing the race. #20994
• Fixed an issue where the automatic module name in hazelcast-5.x.jar could not be detected using Gradle. The reason was /META-INF/MANIFEST.MF not being the first or second entry in the JAR file; now this manifest file is the second entry. #20976

v5.1.1

This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast Platform 5.1.1 release. The numbers in the square brackets refer to the issues in Hazelcast's GitHub repositories.

... (truncated)

Commits

• 5b7b269 version update for 5.1.4 release
• eba69db Platform OS 5.1.4 release notes.
• 2bcd87d prepare release 5.1.4
• 8c65aee Bump jackson.version from 2.13.3 to 2.13.4 [5.1.z] (#22419)
• cd217c2 Fixed ClearBackupOperation [HZ-1210][BACKPORT] (#22082) (#22408)
• 37bd536 Update vulnerable snakeyaml dependency [5.1.z] (#22404)
• 9a682d4 [CN-399] [BACKPORT] Change Kubernetes client behavior for token refresh (#22394)
• 666e7d5 [CN-360] [BACKPORT] [5.1.z] Add multiple label support for Kubernetes Plugin ...
• 1036e67 [CN-169] do not rely on optonal Endpoint nodeName (backport) (#22403)
• c9747a9 [HZ-1138] [BACKPORT] Add missing expiry merge for WAN (#22294) (#22336)
• 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 #98.