Skip to content

MODEXPS-314 - Upgrade dependencies for Kafka 4.2 compatibility in mod-data-export-spring#379

Merged
siarhei-charniak merged 1 commit into
masterfrom
MODEXPS-314
Jun 9, 2026
Merged

MODEXPS-314 - Upgrade dependencies for Kafka 4.2 compatibility in mod-data-export-spring#379
siarhei-charniak merged 1 commit into
masterfrom
MODEXPS-314

Conversation

@siarhei-charniak

Copy link
Copy Markdown
Contributor

MODEXPS-314 - Upgrade dependencies for Kafka 4.2 compatibility in mod-data-export-spring

Purpose

Update the required dependencies to enable support for Kafka 4.2 and ensure compatibility with the newer Kafka version in mod-data-export-spring.

Approach

Updated Kafka version, effective POM contains correct value:
Screenshot 2026-06-08 at 21 50 08

Pre-Merge Checklist:

Before merging this PR, please go through the following list and take appropriate actions.

  • Does this PR meet or exceed the expected quality standards?
    • Code coverage on new code is 80% or greater
    • Duplications on new code is 3% or less
    • Check logging
    • There are no major code smells or security issues
  • Does this introduce breaking changes?
    • Were any API paths or methods changed, added or removed?
    • Were there any schema changes?
    • Did any of the interface versions change?
    • Were permissions changed, added, or removed?
    • Are there new interface dependencies?
    • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

  • What other modules will these changes impact?
  • Do JIRAs exist to update the impacted modules?
    • If not, please create them
    • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
    • Do they have all they appropriate links to blocked/related issues?
  • Are the JIRAs under active development?
    • If not, contact the project's PO and make sure they're aware of the urgency.
  • Do PRs exist for these changes?
    • If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

@siarhei-charniak siarhei-charniak requested a review from a team June 8, 2026 18:57
@siarhei-charniak siarhei-charniak self-assigned this Jun 8, 2026
@sonarqubecloud

sonarqubecloud Bot commented Jun 8, 2026

Copy link
Copy Markdown

@siarhei-charniak siarhei-charniak merged commit 1468f77 into master Jun 9, 2026
17 checks passed
@siarhei-charniak siarhei-charniak deleted the MODEXPS-314 branch June 9, 2026 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants