Merge remote-tracking branch 'refs/remotes/upstream/v/5.4' into v/5.4

docs/antora.yml

@@ -8,11 +8,11 @@ display_version: '5.4'
 asciidoc:
   attributes:
     # The full major.minor.patch version, which is used as a variable in the docs for things like download links
-    full-version: '5.4.0'
+    full-version: '5.4.1'
     # The minor.patch version, which is used as a variable in the docs for things like file versions
     minor-version: '5.3'
     # The snapshot version for installing with brew
-    version-brew: '5.4.0'
+    version-brew: '5.4.1'
     # Allows us to use UI macros. See https://docs.asciidoctor.org/asciidoc/latest/macros/ui-macros/
     experimental: true
     page-toclevels: 1@

docs/modules/ROOT/nav.adoc

@@ -42,6 +42,8 @@
 ** xref:migrate:migration-tool-imdg.adoc[]
 *** xref:migrate:dmt-command-reference.adoc[]
 * xref:release-notes:releases.adoc[Release notes]
+** xref:release-notes:5-4-1.adoc[5.4.1]
+** xref:release-notes:5-4-0.adoc[5.4.0]
 // * xref:placeholder.adoc[Troubleshooting]
 // * xref:placeholder.adoc[FAQ]
 

docs/modules/cp-subsystem/pages/configuration.adoc

@@ -120,7 +120,7 @@ you should xref:cp-subsystem:management.adoc#destroying-a-cp-group-by-force[dest
 
 Some CP members are better leadership candidates than others. For example, members in your primary data center make better leaders because of the reduced latency between clients and the leader. Whereas, members under high load are not good candidates because they are more likely to suffer from downtime. To ensure the availability of the CP subsystem, you can configure CP members with a priority rating, using the <<cp-member-priority, `cp-member-priority`>> option.
 
-Initially, any CP member with any priority can become a leader. But, the leadership rebalancing task periodically transfers the leadership from CP members with the lowest priorities to those with higher priorities within each CP group. Eventually, all CP group leaders are CP members with high priorities.
+Initially, any CP member with any priority can become a leader (`cp-member-priority` is not therefore taken into account during the leader election processes). But, the backgound leadership rebalancing task periodically transfers the leadership from CP members with the lowest priorities to those with higher priorities within each CP group. Eventually, all CP group leaders are CP members with high priorities.
 
 NOTE: Only CP members that are part of a CP group can become leaders. CP members that are not in a CP group do not participate in the leadership rebalancing task. For example, you start a cluster with the CP group size set to three and three CP members with priority 0. Later, you promote a new CP member with priority 100. Even though it has a higher priority, the new CP member never becomes a leader because the CP group is full. The new CP member is eligible for leadership only when a CP member leaves the CP group and the new CP member takes the previous member's place.
 

docs/modules/release-notes/pages/5-4-1.adoc

@@ -0,0 +1,16 @@
+= 5.4.1 Release Notes
+
+== Enhancements
+
+* Introduced a new YAML configuration option for User Code Namespaces that enables multiple name spaces to be defined within a `name-spaces` collection [#2485]. For more info, see xref:clusters:ucn-member-side.adoc[].
+
+== Fixes
+
+* Exclude non-WAN address aliases during WAN MemberHandshake (#2418)
+* Fix NullPointerException in NotifyMemberShutdownOperation during RU (#1727)
+* JobConfig#add not using derived id for some resources (#1723)
+* Vulnerabilities in protobuf-java 3.19.4 and hadoop-shaded-protobuf_3_7-1.1.1 https://github.com/hazelcast/hazelcast/issues/22541[#22541]
+* Vulnerability in hadoop-shaded-guava-1.1.1.jar (shaded: com.google.guava:guava:30.1.1-jre) https://github.com/hazelcast/hazelcast/issues/24981[#24981]
+* Vulnerability in aircompressor-0.21 https://github.com/hazelcast/hazelcast/issues/26354[#26354]
+
+

docs/modules/release-notes/pages/releases.adoc

@@ -1,3 +1,4 @@
 = Hazelcast Platform 5.4.x release notes
 
+* xref:release-notes:5-4-1.adoc[5.4.1]
 * xref:release-notes:5-4-0.adoc[5.4.0]