Dev News Daily ENDE

Spring for Apache Pulsar moves into the Apache Pulsar project; 2.0.8 is the last Spring release

The Spring team announced on 10 November that Spring for Apache Pulsar is leaving the Spring portfolio. The project becomes a subproject of Apache Pulsar at the Apache Software Foundation and will be called Apache Pulsar support for Spring. Jason Konicki, who wrote the announcement, gives the reason as closer collaboration with the Pulsar community and keeping the integration in step with how Pulsar itself changes.

The practical part is about versions. Spring for Apache Pulsar 2.0.8 is the final release under the Spring umbrella. After it, the Spring team will publish no further updates, maintenance patches or bug fixes for the project in current or future Spring release trains. Maintenance, features, fixes, support and releases move to the Apache Pulsar project.

Two related pieces move with it. The Spring Boot starter for Pulsar will no longer be maintained by Spring; version 2.0.8 stays available with Spring Boot 4.2.0, and for later releases users are told to switch to the starter published by the new Apache project. The Spring Cloud Stream binder for Pulsar will still ship once more inside Spring Cloud Stream 5.1.0; after that release it too has to be taken from the Apache Pulsar support for Spring project.

For existing applications nothing breaks immediately. The announcement says they can keep using 2.0.8, and the 5.1.0 binder, safely. To get updates and new features, though, teams will have to change dependency coordinates and package imports to the new project. The Spring post points to an announcement from the Apache Pulsar project for the details of the new coordinates.

Spring for Apache Pulsar moves into the Apache Pulsar project; 2.0.8 is the last Spring release
Spring for Apache Pulsar moves into the Apache Pulsar project; 2.0.8 is the last Spring release — Dev News Daily

Why it matters

A change of coordinates and packages is the kind of migration that is easy to postpone until a security fix forces it. Teams running Pulsar under Spring Boot have a clear marker now: anything after 2.0.8 comes from Apache, so the dependency change belongs on the plan before the next patch is needed, not after.