Skip to content

fix(deps): align all io.netty:* to 4.2.13.Final via netty-bom#24048

Open
stian-sandvold wants to merge 1 commit into
2.43from
chore/align-netty-bom-4.2.13-2.43
Open

fix(deps): align all io.netty:* to 4.2.13.Final via netty-bom#24048
stian-sandvold wants to merge 1 commit into
2.43from
chore/align-netty-bom-4.2.13-2.43

Conversation

@stian-sandvold
Copy link
Copy Markdown
Contributor

What

Bumps netty-all from 4.2.1.Final to 4.2.13.Final and imports the netty-bom in dependency management so that every io.netty:* module on the classpath resolves to one consistent version.

Why

We currently pin netty-all (an uber jar) to one version, but the individual netty modules pulled in transitively — via Artemis, reactor-netty and others — are free to resolve to older versions. That mix on a single classpath leads to runtime failures like AbstractMethodError and NoClassDefFoundError (for example a missing io/netty/util/LeakPresenceDetector), which a green compile does not catch.

Importing the netty-bom forces all netty modules to the same 4.2.13.Final, removing the skew.

Notes

🤖 Generated with Claude Code

Bumps netty-all 4.2.1.Final -> 4.2.13.Final and imports netty-bom so that
every io.netty:* module on the classpath resolves to a single, consistent
version. Without the BOM the netty-all uber jar mixes with older individual
netty modules pulled transitively (e.g. via Artemis and reactor-netty),
which causes runtime errors such as AbstractMethodError and
NoClassDefFoundError (e.g. io/netty/util/LeakPresenceDetector).

This mirrors the alignment already on the 2.41 and 2.42 branches and closes
the same gap on 2.43. It also unblocks the reactor-netty-http 1.3.5 upgrade
(#23878), which references netty classes only present in newer 4.2.x.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@sonarqubecloud
Copy link
Copy Markdown

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.

1 participant