Bump com.hazelcast:hazelcast from 5.1 to 5.3.6

[dependabot[bot]]

Bumps com.hazelcast:hazelcast from 5.1 to 5.3.6.

Release notes

Sourced from com.hazelcast:hazelcast's releases.

v5.3.6

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

Fixes

• Fixed a WAN replication failure - when using maps with WAN replication enabled, and BINARY or NATIVE in-memory formats for the entries, WAN replication was failing when an entry is updated with the same key/value pair, and the cluster members lack serialization information. #25899

v5.3.5

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

NOTE: Due to an error in the tooling, the Platform releases 5.3.3 and 5.3.4 needed to be skipped numerically.

Enhancements

• Improved the permission checks by fixing the CVE-2023-45859 and CVE-2023-45860 vulnerabilities.
• Changed the exception type from CancellationException to CancellationByUserException in case the user cancels a job before it is initialized. #25452
• Updated the versions of the following dependencies
  • gRPC to 1.57.0, #25430
  • Netty to 4.1.100, #25670
  • Avro to 1.1.13, #25659
  • Snappy Java to 1.1.10.5
  • Elasticsearch to 7.17.13, #25660
• Renamed the service port for Hazelcast clusters deployed in Kubernetes environments as hazelcast. Previously, the name was hazelcast-service-port causing the member auto-discovery (for embedded deployments) to fail. #24834

Fixes

• Fixed an issue where the map entries' metadata, such as time-to-live and expiration, was not replicated correctly over WAN after updating existing entries. #25505
• Fixed an issue where the member list was not updated after a cluster failover scenario. #25504
• Fixed a memory leak issue happening in Hazelcast members and clients while destroying fenced locks. #25421

Removed/Deprecated Features

• Removed the evaluation tool (to try out Platform 5.x features for IMDG 3.x users) and the relevant IMDG 3.x JAR libraries from Hazelcast Platform distributions. #25663

v5.3.2

This document lists the enhancements and fixed issues for Hazelcast Platform 5.3.2 release. The numbers in the square brackets refer to the issues and pull requests in Hazelcast's GitHub repository.

Enhancements

• Updated the Janino dependency version to 3.1.10. #25094

Fixes

• Renamed the service port for Hazelcast clusters deployed in Kubernetes environments as hazelcast. Previously, the name was hazelcast-service-port causing the member auto-discovery (for embedded deployments) to fail. #25228
• Fixed an issue where the getDistributedObjects() was returning inconsistent results when multiple members are simultaneously joining to the cluster. #25153
• Fixed an issue where the Hot Restart procedure was failing on Hazelcast Viridian, when the cluster is in the FROZEN state. #25081
• Fixed an issue where the retry mechanism for the communications between CP leader and followers was generating too many retries, due to incorrect backoff timeout reset behavior. #25074

... (truncated)

Commits

• 6209577 Upgrade version to 5.3.6
• 9903dc9 Adding RN for Platform OS 5.3.6 (#25949)
• 2078171 Compare raw values when merging expiration in WAN [HZ-3661] [5.3.6] (#25932)
• 22cc289 Update POM version manually to 5.3.6-SNAPSHOT [HZ-3673][5.3.6] (#25911)
• 7e760b0 Upgrade version to 5.3.5
• 0a8cc63 Adding note to 5.3.5 OS RN. (#25829)
• ae0396d Update version of dependency-check-maven to 8.4.2 (#25816)
• b2c44b5 Fix 5.3.4 deployment by pushing 5.3.5 (#25800)
• 781beef Check permissions during the validation for dynamic functions [HZ-3516] [5.3....
• b7c8d0d Bump everit-json-schema to mitigate CVE-2023-5072 [HZ-3518] [5.3.3] (#25773)
• 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 show 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)

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 1 day

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.