• DB2 (flyway-database-db2)

• Derby (flyway-database-derby)

• HSQLDB (flyway-database-hsqldb)

• Informix (flyway-database-informix)

• PostgreSQL (flyway-database-postgresql)

• Redshift (flyway-database-redshift)

• SAP HANA (flyway-database-saphana)

• Snowflake (flyway-database-snowflake)

• Sybase ASE (flyway-database-sybasease)

Native Build Tools

If you’re using the Native Build Tools to build your project with GraalVM, make sure you’re using at least a 0.10.x version of the plugin. Maven users should get the correct version automatically when using the Spring Boot parent.

Gradle users should update the plugin version in the plugins block:

plugins {
  // ...
  id 'org.graalvm.buildtools.native' version '0.10.2'
  // ...
}

java -Djarmode=tools -jar your-application.jar extract

• extract, as shown above. This supersedes -Djarmode=layertools extract.

• list-layers, which supersedes -Djarmode=layertools list-layers.

java -Djarmode=tools -jar your-application.jar help <command>

Spring for Apache Pulsar

The properties spring.pulsar.listener.observation-enabled and spring.pulsar.template.observations-enabled changed their default value from true to false. This has been done to unify the observation-enabled properties, all of which now default to false. If you were relying on Pulsar observations and didn’t enable them explicitly, add the properties spring.pulsar.listener.observation-enabled=true and spring.pulsar.template.observations-enabled=true to your configuration to restore the old behavior.

Brave and Zipkin

Brave has been updated to 6.0, and Zipkin to 3.0. With that upgrade, the Zipkin support in Spring Boot got new features, like specifying the encoding in which data is reported to the Zipkin API. See #39049 for details.

A new JDK HttpClient based Zipkin sender has been implemented. This sender only depends on the JDK and will be the default sender in Spring Boot 3.5.0, superseding the WebClient and RestTemplate sender implementations.

• spring.security.oauth2.resourceserver.jwt.authority-prefix

• spring.security.oauth2.resourceserver.jwt.principal-claim-name

• spring.security.oauth2.resourceserver.jwt.authorities-claim-name

Support for Apache ActiveMQ Artemis

Service connection support for Apache ActiveMQ Artemis has been added. The Testcontainers support works with the ArtemisContainer container, the Docker Compose support works with the apache/activemq-artemis image.

Support for the official ActiveMQ Classic images

The ActiveMQ service connection now supports the apache/activemq-classic docker image and the ActiveMQContainer testcontainer.

Support for LDAP

Service connection support for LDAP with the osixia/openldap container has been added

Bitnami Container Images

The Spring Boot support for Docker Compose will detect and configure containers from Bitnami in addition to official images for several of the supported technologies, including Cassandra, Elasticsearch, MariaDB, MySQL, MongoDB, Neo4j, PostgreSQL, RabbitMQ, and Redis. See the updated reference documentation for more information.

spring:
  ssl:
    bundle:
      pem:
        mybundle:
          keystore:
            certificate: "base64:LS0tLS1CRUdJTi..."
            private-key: "base64:QmFnIEF0dHJpYn..."

• 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

• The started log messages produced by the four supported web servers (Jetty, Netty, Tomcat, and Undertow) are now more consistent

• Added client-id and subscription-durable properties for JMS connections

• If a class implements multiple servlet interfaces, like Filter or Servlet, it will now be registered for all of the interfaces (e.g. one registration for a filter and one for a servlet)

• The new reactive sessions actuator endpoint can now return sessions for a given username

• The environment’s default profiles are now included in the env actuator endpoint’s response

• Added the new property spring.liquibase.ui-service to specify the default UI service logger used by Liquibase

• Added the new property spring.security.saml2.relyingparty.registration.*.name-id-format to specify the NameID format of a SAML registration

• Added the new property server.mime-mappings which allows additional custom MIME type mappings to be configured

• jakarta.inject:jakarta.inject-api is now included in Spring Boot’s dependency management

• The date format of the git-commit-id-maven-plugin has been changed to yyyy-MM-dd’T’HH:mm:ssXXX to allow reproducible builds. See #39606 for details

• The spring-boot-starter-jetty no longer includes jetty-jndi by default. If you need JNDI support, please add org.eclipse.jetty:jetty-jndi to your dependencies

• On Windows it’s now possible to start the application with mvn spring-boot:run even if it has an extremely large number of dependencies. Before 3.3.0 it would fail with a "The filename or extension is too long" exception due to the length of the classpath

• The new property spring.data.jdbc.dialect can be used to set the dialect for Spring Data JDBC. If not set, the dialect will be auto-detected

• Add more gap between the orders of CloudFoundryVcapEnvironmentPostProcessor and ConfigDataEnvironmentPostProcessor

• The Cassandra driver changed coordinates from com.datastax.oss to org.apache.cassandra

• Setting the new property management.observations.long-task-timer.enabled to false now prevents the creation of a LongTaskTimer for every observation

• Beans in the infrastructure role are now automatically excluded from lazy initialization

• Spring Config now uses the conversion service from the environment when resolving properties

• Set the new property spring.docker.compose.start.skip to never to always execute the Docker Compose startup command

• A new spring.graphql.websocket.keep-alive property has been added

• JPA auto-configuration now uses a ManagedClassNameFilter bean if one is defined

• A new spring.rabbitmq.template.allow-list-patterns property has been added