Spring Boot 2.6.2 Release: Key Bug Fixes, Docs Updates, and Dependency Upgrades

Spring Boot 2.6.2, released on December 21, introduces 55 bug fixes, documentation improvements, and a comprehensive set of dependency upgrades, providing developers with more stable configuration binding, corrected database initialization, enhanced security handling, and updated libraries across the ecosystem.

Java Architecture Diary
Java Architecture Diary
Java Architecture Diary
Spring Boot 2.6.2 Release: Key Bug Fixes, Docs Updates, and Dependency Upgrades

On December 21, the official Spring Boot 2.6.2 version was released, containing 55 bug fixes, documentation improvements, and dependency upgrades.

<parent>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-parent</artifactId>
  <version>2.6.2</version>
  <relativePath/>
</parent>

Bug Fixes

When a getter or setter is overridden to use a subclass of the property type, the getter and setter used during configuration property binding differ. DatabaseInitializationDependencyConfigurer triggered eager loading of factory beans.

In Spring Boot 2.6.0, Quartz could not create tables on mysql / mariadb databases.

Database platform initialization for Quartz, Session, Integration, and Batch could not be configured.

The dependency thymeleaf-extras-springsecurity5 without the accompanying Spring Security caused application startup failures.

When using Spring Security, ResponseStatusException no longer returned a response body.

Even when DatabaseInitializationMode is set to never, DataSourceScriptDatabaseInitializer still attempts to access the database.

In Spring Boot 2.6.1, setting useCodeAsDefaultMessage to true broke Hibernate validation messages.

If no tag is set for the built image, the latest tag is not applied by default.

Compiling a WAR with Maven produced an invalid class‑path index manifest attribute.

When deploying to a Servlet 3.1‑compatible container,

org.springframework.boot.web.servlet.filter.ErrorPageSecurityFilter

caused an abstract method error.

Setting the health‑check endpoint cache time-to-live property had no effect.

The property server.servlet.session.cookie.same-site could not be applied to cookies created by Spring Session.

Documentation Improvements

2.5.x snapshot documentation now links to source code on the main branch.

Added documentation that WebFlux does not support using DevTools with remote applications.

Added guidance on creating custom auto‑configuration sections in the core reference documentation.

Added a CacheManager customization section to the reference documentation.

Published the README.adoc.

Fixed the recorded default value for the property spring.mvc.pathmatch.matching-strategy.

Added consistent quoting to YAML examples in the reference documentation.

Dependency Upgrades

Logback 1.2.9

AppEngine SDK 1.9.93

Caffeine 2.9.3

Couchbase Client 3.2.4

DB2 JDBC 11.5.7.0

Dropwizard Metrics 4.2.7

Ehcache3 3.9.9

Flyway 8.0.5

Hazelcast 4.2.4

Hibernate 5.6.3.Final

HttpAsyncClient 4.1.5

HttpCore 4.4.15

Infinispan 12.1.10.Final

Jackson Bom 2.13.1

JDOM2 2.0.6.1

Jedis 3.7.1

JUnit Jupiter 5.8.2

Kotlin 1.6.10

Log4j2 2.17.0

Micrometer 1.8.1

MSSQL JDBC 9.4.1.jre8

Netty 4.1.72.Final

Reactor 2020.0.14

Spring AMQP 2.4.1

Spring Framework 5.3.14

Spring Integration 5.5.7

Spring Kafka 2.8.1

Spring LDAP 2.3.5

Spring Security 5.6.1

Spring Session 2021.1.1

Spring WS 3.1.2

Thymeleaf 3.0.14.RELEASE

Tomcat 9.0.56

Undertow 2.2.14.Final

XmlUnit2 2.8.4

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

JavaBackend DevelopmentSpring BootBug FixesRelease Notesdependency-upgrade
Java Architecture Diary
Written by

Java Architecture Diary

Committed to sharing original, high‑quality technical articles; no fluff or promotional content.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.