Spring Boot 3.3.0 M1 Release Notes

Spring Boot 3.3.0-M1 Release Notes

Dependency Management for Dropwizard Metrics Removed

Dependency management for Dropwizard Metrics has been removed. Spring Boot does not depend directly upon Dropwizard Metrics and, therefore, does not require a specific version. If your application depends on Dropwizard Metrics directly, update your build configuration to specify a version that meets its needs.

Upgrading from Spring Boot 3.2

Minimum Requirements Changes

None.

New and Noteworthy

Tip	Check the configuration changelog for a complete overview of the changes in configuration.

Observability Improvements

Observations can now be enabled for the simple, direct and stream listener and on the RabbitTemplate via properties.

Support for the Micrometer @SpanTag annotation has been added.

Added support for tagged fields for both Brave and OpenTelemetry. Support for local fields has been added for Brave.

Added a process InfoContributor, which can be enabled with management.info.process.enabled=true.

Dependency Upgrades

Spring Boot 3.3.0-M1 moves to new versions of several Spring projects:

…

Numerous third-party dependencies have also been updated, some of the more noteworthy of which are the following:

…

Miscellaneous

Apart from the changes listed above, there have also been lots of minor tweaks and improvements including:

spring.config.activate.on-cloud-platform=none will now match when the active cloud platform is null.
Added a configuration option for "path" field inclusion in error responses. This can be controlled by the server.error.include-path property. It defaults to always.
The WebFlux DefaultErrorAttributes now use request.requestPath().value() to populate path error attribute.
Added the property server.tomcat.threads.max-queue-capacity to configure the maximum queue size for the Tomcat web server connector.
The configuration processor now checks the additional-spring-configuration-metadata.json for superfluous keys and fails if it encounters any.
Added a property named spring.task.execution.pool.shutdown.accept-tasks-after-context-close to control if the ThreadPoolTaskExecutor accepts tasks after the context shutdown has been initiated.
Added the property server.reactive.session.max-sessions to control the number of maximum sessions when using WebFlux.
ExecutionContextSerializer beans are now automatically applied to the Spring Batch configuration. If none is provided, DefaultExecutionContextSerializer is used.