Any plans for a 4.2.3 release? (DNS-resolver shutdown fix #26045)

[David Kjerrumgaard via dev <de...@pulsar.apache.org>]

Hi all,

I'd like to ask about the timeline for a 4.2.3 release.

The fix in #26045 — "Prevent client shutdown from leaking event loop
threads when DNS resolver close fails" — was merged to master and
cherry-picked to branch-4.2 (commit 2baa1f7e6) on June 17. There's no
v4.2.3 candidate tag yet, so I wanted to surface a downstream need.
▎
This fix is currently blocking a Quarkus upgrade (quarkusio/quarkus#54516).
The Quarkus smallrye-reactive-messaging-pulsar extension can't move past
pulsar-client 4.2.1 — without this fix, the DNS-resolver leak causes JVM
tests to hang on client shutdown. We've validated 4.2.x end-to-end against
the extension (native image work is green at 4.2.2, and the regression test
added in #26045 confirms the fix), so a published 4.2.3 on Maven Central is
the only remaining blocker on our side.

Is a 4.2.3 release on the near-term roadmap? If a release manager is
willing to cut one, I'm happy to help test a release candidate against the
Quarkus extension to validate it before the vote closes.▎

Thanks for considering,

David Kjerrumgaard

Principal Sales Engineer

Las Vegas, Nevada

<https://streamnative.io/> <https://github.com/david-streamlio>
<https://www.linkedin.com/in/davidkj/>  <https://x.com/streamnativeio>
<https://www.youtube.com/channel/UCywxUI5HlIyc0VEKYR4X9Pg>

-- 
This email and any attachments are intended solely for the recipient(s) 
named above and may contain confidential, privileged, or proprietary 
information. If you are not the intended recipient, you are hereby notified 
that any disclosure, copying, distribution, or reproduction of this 
information is strictly prohibited. If you have received this email in 
error, please notify the sender immediately by replying to this email and 
delete it from your system.

Re: Any plans for a 4.2.3 release? (DNS-resolver shutdown fix #26045)

[Lari Hotari <lh...@apache.org>]

I can start a release asap.

-Lari

ke 24.6.2026 klo 20.51 David Kjerrumgaard via dev <de...@pulsar.apache.org>
kirjoitti:

> Hi all,
>
> I'd like to ask about the timeline for a 4.2.3 release.
>
> The fix in #26045 — "Prevent client shutdown from leaking event loop
> threads when DNS resolver close fails" — was merged to master and
> cherry-picked to branch-4.2 (commit 2baa1f7e6) on June 17. There's no
> v4.2.3 candidate tag yet, so I wanted to surface a downstream need.
> ▎
> This fix is currently blocking a Quarkus upgrade (quarkusio/quarkus#54516).
> The Quarkus smallrye-reactive-messaging-pulsar extension can't move past
> pulsar-client 4.2.1 — without this fix, the DNS-resolver leak causes JVM
> tests to hang on client shutdown. We've validated 4.2.x end-to-end against
> the extension (native image work is green at 4.2.2, and the regression test
> added in #26045 confirms the fix), so a published 4.2.3 on Maven Central is
> the only remaining blocker on our side.
>
> Is a 4.2.3 release on the near-term roadmap? If a release manager is
> willing to cut one, I'm happy to help test a release candidate against the
> Quarkus extension to validate it before the vote closes.▎
>
> Thanks for considering,
>
> David Kjerrumgaard
>
> Principal Sales Engineer
>
> Las Vegas, Nevada
>
> <https://streamnative.io/> <https://github.com/david-streamlio>
> <https://www.linkedin.com/in/davidkj/>  <https://x.com/streamnativeio>
> <https://www.youtube.com/channel/UCywxUI5HlIyc0VEKYR4X9Pg>
>
> --
> This email and any attachments are intended solely for the recipient(s)
> named above and may contain confidential, privileged, or proprietary
> information. If you are not the intended recipient, you are hereby
> notified
> that any disclosure, copying, distribution, or reproduction of this
> information is strictly prohibited. If you have received this email in
> error, please notify the sender immediately by replying to this email and
> delete it from your system.
>