What’s New in Spring Boot 2.6.1? Key Bug Fixes and Docs Updates
Spring Boot 2.6.1, released on November 29, brings 11 bug fixes and documentation improvements to support the upcoming Spring Cloud 2021, addressing issues from pattern parsing to security filters, Lettuce integration, MockMvc configuration, and Elasticsearch dependency handling.
Release Notes
On November 29, Spring Boot 2.6.1 was officially released, primarily to support the upcoming Spring Cloud 2021.
This version includes 11 bug fixes and documentation improvements .
Bug Fixes
Corrected the name of the matching-strategy attribute in the operation message of PatternParseException (#28839).
Fixed compatibility issue of ErrorPageSecurityFilter when deployed to Servlet 3.1 (#28790).
Added mapping for MariaDB in QuartzDataSourceScriptDatabaseInitializer (#28779).
Corrected the order of property sources for "test" and "Inlined Test Properties" (#28776).
Resolved ArrayStoreException when using Spring Security in a Servlet application without spring-security-web (#28774).
Fixed warning where DefaultClientResources did not close properly when using Lettuce with Actuator (#28767).
Addressed issue where pages with permitAll could no longer be accessed via auto-configured MockMvc (#28759).
Ensured dependency management for org.elasticsearch.distribution.integ-test-zip:elasticsearch declares its type as zip (#28746).
Documentation
Fixed a typo in the "External Application Properties" section of the documentation (#28834).
Corrected the output example for spring --version in the reference documentation (#28833).
Added a description for the org.springframework.boot.actuate.metrics.data package (#28761).
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java Architecture Diary
Committed to sharing original, high‑quality technical articles; no fluff or promotional content.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.