Skip to content

Conversation

@d4v1de
Copy link
Collaborator

@d4v1de d4v1de commented Dec 19, 2025

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
high severity Allocation of Resources Without Limits or Throttling
SNYK-JAVA-ORGBITBUCKETBC-14465261
  828   org.apache.kafka:connect-runtime:
3.3.2 -> 4.1.0
Major version upgrade Proof of Concept

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • 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 fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

@d4v1de
Copy link
Collaborator Author

d4v1de commented Dec 19, 2025

Merge Risk: High

This major version upgrade removes ZooKeeper support, requiring a mandatory migration to KRaft mode before upgrading. It also removes deprecated APIs and introduces significant changes to Kafka Streams.

ZooKeeper Mode Removed: Apache Kafka 4.0 and newer no longer support ZooKeeper. Clusters must be fully migrated to KRaft mode before upgrading the server/client versions. The cluster's software and metadata versions must be at least 3.3.x before beginning the upgrade to 4.x. [11]
API Removals: Many deprecated APIs have been removed. For Kafka Streams users, KStreams#transformValues() was removed and must be replaced with KStreams#processValues(). [11]

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants