Bump hazelcast from 3.12.5 to 4.1.2

[dependabot-preview]

Bumps hazelcast from 3.12.5 to 4.1.2.

Release notes

Sourced from hazelcast's releases.

v4.1.2

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

Fixes

• Fixed an issue where the Java client was not receiving membership events when a member with Hot Restart Persistence is restarted. #18268
• Fixed an issue where the Near Cache configuration of a map in client was not the same after the client is recreated with the same client failover configuration. #18356
• Fixed an issue that prohibited Hazelcast from being used as Tomcat session manager when it is also deployed in a web application context: When a client application that uses Hazelcast tries to connect to the Hazelcast cluster and this application's web sessions are persisted using Hazelcast's Tomcat session manager, the session manager could not connect to the cluster. This has been fixed by improving Hazelcast's service loader mechanism. #18116
• Fixed an issue where the metrics for map hits statistics in Management Center were decreasing as the map entries are being expired. #18112
• When the in-memory format of a map is NATIVE and the uploaded user code has missing classes (in case the user code deployment feature is used), the resulting exception could not be seen on the client side when a map query is run. This was causing the client to hang indefinitely and fixed by improving the failure handling for this case. #18084
• Fixed an issue where the queue items were being delivered more than once when they are reproduced after a member leaves the cluster. #18057
• When the user code deployment is used and the classes to be deployed have com.hazelcast prefix, it was causing failures in other Hazelcast products, e.g., Jet. This has been fixed by making use of the context classloader when loading such classes. #17915
• The -c parameter of the cp-subsystem.sh script was used for both cluster name and group variables. This has been fixed by introducing the -g parameter for groups. #17907
• Fixed an issue where the remove() and delete() operations of maps were not updating the local map statistics. #17750

v4.1.1-migration

No release notes provided.

v4.1.1

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

New Features

• Node Aware Partition Grouping: Added the support of partition grouping mechanism in the Hazelcast discovery plugin for Kubernetes. You can create partition groups according to the name of the node which is provided by this plugin and on which the containers/pods run. See the NODE_AWARE section of the IMDG Reference Manual for more information.

Enhancements

... (truncated)

Commits

• 7a3f273 version update for 4.1.2 release
• dafe83c Add selectionKey null check in NioOutboundPipeline.executePipeline to prevent...
• 31ae87d Updating the PR number for an entry in 4.1.2 RN.
• f528415 Move connectioClose back to member event handling
• 683a5c6 Copy Nearcacheconfig when it needs to be changed
• b0eb5e3 Revert "Make NearcacheConfig equal before and after it is used"
• a698d46 Adding the IMDG OS 4.1.2 release_notes.txt
• c185dd3 prepare release 4.1.2
• 4303778 Check memberlist snapshot before clearing it (#18279)
• 565f9ae Fire membership evetns when persistence enabled
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @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 your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• 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)

[dependabot-preview]

Superseded by #110.