Thanks again for helping updating the dependencies; I've sent out a vote
for flink-shaded 21.0 [1]

Best regards,

Martijn

[1] https://lists.apache.org/thread/tyz8v1b4c7flxpzqvr8or9v7kq242f3f

On Sun, Nov 30, 2025 at 7:24 PM Mate Czagany <[email protected]> wrote:

> Hi Martijn,
>
> I have created a PR for updating the dependencies to the latest version at
> the time of the commits [1]. I've also opened another PR as a hotfix, as
> the license check CI currently doesn't actually check anything without and
> will always be green [2].
>
> Best regards,
> Mate
>
> [1] https://github.com/apache/flink-shaded/pull/153
> [2] https://github.com/apache/flink-shaded/pull/154
>
> On Mon, Nov 17, 2025 at 6:29 PM Mate Czagany <[email protected]> wrote:
>
> > Hi Martijn,
> >
> > That's a great idea, I will look into it this week.
> >
> > Thank you,
> > Mate
> >
> > On Mon, Nov 17, 2025 at 5:10 PM Martijn Visser <[email protected]
> >
> > wrote:
> >
> >> Hi Mate,
> >>
> >> I would happily help out with driving the release, but I think we should
> >> check if there are other dependencies that could also use a bump, and do
> >> those too. Could you take a look at those?
> >>
> >> Best regards,
> >>
> >> Martijn
> >>
> >> On Mon, Nov 17, 2025 at 8:50 AM Mate Czagany <[email protected]>
> wrote:
> >>
> >> > Hi!
> >> >
> >> > I would like to propose the release of flink-shaded 21.0, which would
> >> > upgrade Netty to a newer, 4.2.x version [1] that would also allow
> Flink
> >> to
> >> > move to a newer Pekko version. This also opens up the possibility to
> >> > release flink-shaded-netty-tcnative-static too, as the version of
> >> BoringSSL
> >> > this new Netty version uses is released under the Apache 2.0 license.
> >> [2]
> >> >
> >> > As I'm not a committer, I cannot drive the release myself, but I'll
> >> happily
> >> > take any tasks that I'm allowed to regarding the release.
> >> >
> >> > Best regards,
> >> > Mate
> >> >
> >> > [1] https://issues.apache.org/jira/browse/FLINK-38320
> >> > [2] https://lists.apache.org/thread/t8p053nqft0v44rlsk9zpl507jq1hk3f
> >> >
> >>
> >
>

Reply via email to