Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion lighty-core/dependency-versions/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -222,7 +222,7 @@
<dependency>
<groupId>org.apache.pekko</groupId>
<artifactId>pekko-stream_3</artifactId>
<version>1.2.1</version>
<version>1.4.0</version>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

While upgrading pekko-stream_3 is good, it's crucial to maintain version consistency across all Pekko modules. Mixing versions of Pekko modules is not supported and can lead to binary incompatibilities and subtle runtime errors.

All other pekko core modules are still on version 1.2.1. Please upgrade them all to 1.4.0 as well.

The following dependencies should be updated:

  • pekko-remote_3 (line 175)
  • pekko-slf4j_3 (line 180)
  • pekko-cluster_3 (line 185)
  • pekko-discovery_3 (line 190)
  • pekko-protobuf-v3_3 (line 195)
  • pekko-coordination_3 (line 200)
  • pekko-distributed-data_3 (line 205)
  • pekko-cluster-tools_3 (line 210)
  • pekko-cluster-sharding_3 (line 215)
  • pekko-actor_3 (line 220)

It's recommended to manage all Pekko dependency versions with a property to ensure they are always in sync, for example:

<properties>
    <pekko.version>1.4.0</pekko.version>
</properties>

...

<dependency>
    <groupId>org.apache.pekko</groupId>
    <artifactId>pekko-stream_3</artifactId>
    <version>${pekko.version}</version>
</dependency>
References
  1. It is a best practice to use the same version for all modules of a library (like Pekko) to avoid binary incompatibilities and unexpected runtime errors. This is often explicitly required by the library's authors.

</dependency>
<dependency>
<groupId>org.apache.pekko</groupId>
Expand Down
Loading