What’s New in Spring Boot 3.0.4? Bug Fixes, Docs, and Dependency Upgrades
Spring Boot 3.0.4 arrives ahead of schedule, fixing 19 issues—including a path‑matching bug that broke bean scanning—while adding documentation updates and upgrading key dependencies such as Couchbase, Jetty, and Spring Framework, providing developers with a more stable backend platform.
Spring Boot 3.0.4 has been released earlier than planned because Spring Framework 6.0.5 introduced an issue where PathMatchingResourcePatternResolver can no longer handle paths containing spaces or special characters, causing beans and controllers to fail scanning. This release includes 19 bug fixes, documentation improvements, and dependency upgrades.
“Project directory with Chinese characters and spaces – a big no‑no! Pay attention!”
🐞 Bug Fixes
Maven plugin now uses local timezone timestamps when outputting timestamps (#34430).
Correct logger class used by
org.springframework.boot.web.embedded.jetty.GracefulShutdown(#34419).
@ConfigurationPropertiesno longer binds record property values during initialization (#34407).
Custom ConfigDataLocationResolver/ConfigDataLoader works with spring-boot-devtools in 3.0.x (#34372).
defaultTracingObservationHandler now follows documentation ordering (#34216).
Spring Boot 3 does not provide configuration for custom red metrics tag keys (#34194).
📔 Documentation
Documentation support for Gradle 8 (#34462).
Batch update processing documentation (#34437).
Add Failover starter connection documentation (#34422).
Fix spelling error in external-config.adoc (#34414).
General spelling fixes (#34398).
Consistent use of plugin DSL in Spring Boot Gradle plugin docs (#34391).
🔨 Dependency Upgrades
Upgrade to Couchbase Client 3.4.3 (#34445).
Upgrade to Dropwizard Metrics 4.2.17 (#34446).
Upgrade to Jetty 11.0.14 (#34447).
Upgrade to Reactor Bom 2022.0.4 (#34444).
Upgrade to Spring Data Bom 2022.0.3 (#34439).
Upgrade to Spring Framework 6.0.6 (#34440).
Upgrade to Spring Kafka 3.0.4 (#34441).
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.