Skip to content

v1.4 and v2.2 Release Notes

Jump to bottom
Tadaya Tsuyukubo edited this page Mar 14, 2026 · 1 revision

Datasource Micrometer v1.4 and v2.2 Release Notes

v1.4 and v2.2 are functionally equivalent releases.

  • v1.4 targets Spring Boot 3.5
  • v2.2 targets Spring Boot 4

New Features

DataSourceType.SPRING_PROXY is now the default proxy strategy

A new JDBC proxy creation strategy, DataSourceType.SPRING_PROXY, has been introduced and is now the default.

This strategy uses Spring Framework’s AOP proxy mechanism (ProxyFactory) to create JDBC proxy objects such as DataSource. Using a Spring proxy allows Spring-based infrastructure to retrieve the original target object when necessary. This enables better compatibility with HikariCP when used with Spring Cloud refresh scope. For example, it allows a HikariDataSource to work correctly with refresh operations provided by Spring Cloud.

See issues #99 and #102 for more details.

If your application depends on the previous behavior (JDK dynamic proxies), you can restore it with:

jdbc.datasource-proxy.type=PROXY

jdbc.hikari.enabled property

A new configuration property has been added:

jdbc.hikari.enabled

This flag determines whether the Hikari-specific observation infrastructure (DataSourceObservationAutoConfiguration.Hikari) should be enabled.
The default value is true. See issue #100.

Miscellaneous

  • Exclude jmh-core from JSqlParser 5.3 dependencies (#96)

Clone this wiki locally