[Snyk] Upgrade org.apache.pekko:pekko-stream_3 from 1.2.1 to 1.4.0

[ihrasko]

Snyk has created this PR to upgrade org.apache.pekko:pekko-stream_3 from 1.2.1 to 1.4.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 2 versions ahead of your current version.

• The recommended version was released 22 days ago.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Summary of Changes

Hello @ihrasko, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a routine dependency update, specifically upgrading the pekko-stream_3 library to its latest recommended version, 1.4.0. This update, automatically generated by Snyk, is crucial for maintaining a secure and stable codebase by incorporating the most recent improvements and vulnerability fixes from the library's developers.

Highlights

• Dependency Upgrade: The org.apache.pekko:pekko-stream_3 dependency has been upgraded from version 1.2.1 to 1.4.0.
• Automated Update: This pull request was automatically generated by Snyk to keep dependencies up-to-date and improve security posture.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, generated by Snyk, upgrades org.apache.pekko:pekko-stream_3 from 1.2.1 to 1.4.0. However, this introduces a version mismatch with other Pekko modules in the project, which remain at version 1.2.1. It is critical to use the same version for all Pekko modules to prevent binary incompatibilities and runtime issues. My review includes a critical comment to address this by updating all Pekko core dependencies to 1.4.0 and suggests using a Maven property to manage these versions consistently in the future.

[gemini-code-assist]

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.