Spring Boot 4.2.0-M1 Adds AMQP 1.0 Support and Buildpack Image Caching
Spring Boot 4.2.0-M1 became available on Maven Central on August 20, 2026, as the first milestone toward the 4.2.0 release. The milestone bundles 113 enhancements, documentation improvements, dependency upgrades, and bug fixes.
The most notable new capability is support for the AMQP 1.0 specification, bringing RabbitMQ-specific messaging features that were previously only reachable through the older AMQP 0-9-1 protocol into Spring Boot's auto-configuration. AMQP 1.0 is an OASIS standard with broader interoperability across message brokers beyond RabbitMQ, so applications adopting it gain a more portable messaging layer without hand-rolling connection and channel management. The milestone also adds image-based build cache support for Cloud Native Buildpacks, letting spring-boot:build-image reuse cached layers from a container registry across build machines and CI runners instead of relying solely on local Docker layer caching — a meaningful speedup for teams building container images in ephemeral CI environments.
As with prior milestones, the Spring team is directing community contributions toward issues tagged "ideal for contribution" in the spring-boot GitHub repository, and full details are available in the milestone's GitHub release notes.
Coordinated Milestone Wave Ships M1s Across the Spring Portfolio, Resolves 90+ CVEs
The week of August 17, 2026 saw a coordinated first-milestone release across nearly the entire Spring portfolio: Spring Boot, Spring Framework, Spring Data, Spring Security, Spring Integration, Spring HATEOAS, Spring Modulith, Spring Batch, Spring AMQP, and Spring for Apache Kafka all shipped M1 releases in the same window. Coordinating milestone timing across projects that depend on each other reduces the churn of chasing snapshot compatibility during early development, since downstream projects can pin to the same milestone train.
Spring Data 2026.1.0-M1 introduces a new RedisJsonTemplate class, providing initial first-class support for Redis's native JSON document type rather than requiring manual serialization through RedisTemplate. Beyond individual feature work, the release wave's most consequential item for production users is security-related: over 90 CVEs were addressed across the affected Spring projects as part of this milestone cycle, spanning transitive dependency upgrades and direct fixes. Teams running Spring applications in production should treat the underlying CVE advisories as the higher-priority read here, even though the fixes themselves ride along with milestone (not yet GA) builds — check the individual project advisories before deciding whether a point-release backport is needed for currently deployed versions.
Read more — InfoQ
Links & Sources
You May Also Enjoy
