What Changed Recently
Nov 2024
Boot 3.4: structured logging, graceful shutdown on by default, @MockBean deprecated.
Nov 20, 2025
Boot 4.0: Spring Framework 7, Jackson 3, modular starters, Undertow dropped.
Jun 10, 2026
Boot 4.1: gRPC support, SSRF filter for HTTP clients.
Jun 30, 2026
Boot 3.5: open-source support ends.
30. What does the modular Spring Boot 4 change for your build?
Boot 4 splits its large jars into small modules named spring-boot-<technology>. Each has a starter and a test starter. Features that used to switch on because a third-party library was on the classpath now need their starter.
The migration guide gives Flyway as the example. The flyway-core dependency alone no longer runs migrations. You need spring-boot-starter-flyway.
spring-boot-starter-web is now spring-boot-starter-webmvc (the old name is deprecated), and packages moved, for example @EntityScan to org.springframework.boot.persistence.autoconfigure.
For a large upgrade, the "classic" starters put every module back on the classpath. Fix the imports, then remove them.
31. What breaks when Boot 4 moves you to Jackson 3?
Jackson 3 changes group IDs and packages from com.fasterxml.jackson to tools.jackson (annotations keep the old package).
Boot now auto-configures a JsonMapper, so a custom ObjectMapper bean no longer replaces Boot's. Define a JsonMapper bean or a JsonMapperBuilderCustomizer.
@JsonComponent became @JacksonComponent, and Boot 4 registers every Jackson module it finds on the classpath. spring.jackson.use-jackson2-defaults=true and a deprecated spring-boot-jackson2 module exist as stop-gaps.
Framework 7 plans to drop Jackson 2 support in 7.2.
32. How do @Retryable and @ConcurrencyLimit in Spring Framework 7 work?
They are core resilience annotations, enabled with @EnableResilientMethods. @Retryable retries on any exception by default: at most 3 retries after the first failure, 1 second apart.
Tune it with includes, maxRetries, delay, multiplier and jitter. It also works on methods returning Mono or Flux.
@Retryable(includes = PartnerUnavailableException.class,
maxRetries = 2, delay = 200, multiplier = 2, jitter = 50)
public Quote fetchQuote(String sku) { ... }
maxRetries = 2 means 3 calls in total; our test run against Framework 7.0.9 counted exactly 3. @ConcurrencyLimit(10) caps parallel calls into a method, a bulkhead without a thread pool. Boot 4 dropped dependency management for Spring Retry.
The resilience chapter has the details; circuit breakers still need Resilience4j.
33. How does API versioning work in Spring Boot 4?
Spring Framework 7 added a version attribute to request mappings. Boot 4 sets how the version is read with properties:
spring.mvc.apiversion.use.header=X-Version
spring.mvc.apiversion.default=1.0.0
@GetMapping(path = "/accounts/{id}", version = "1.1")
Account getAccountV11(@PathVariable long id) { ... }
The version can come from a header, a query parameter, a media type parameter or the path. "1.2+" matches 1.2 and later, so a new version needs mappings only for the endpoints that changed.
An ApiVersionDeprecationHandler can add deprecation headers to old versions. See API versioning in the Framework docs.
34. What did Spring Boot 4.1 add?
The 4.1 release notes list these as the ones worth knowing in an interview.
- gRPC: gRPC servers and clients through Spring gRPC 1.1. They run on Netty or in the servlet container over HTTP/2.
- SSRF protection: an
InetAddressFilter on the HTTP clients blocks calls to chosen addresses, such as cloud metadata endpoints.
- Lazy JDBC connections:
spring.datasource.connection-fetch=lazy takes a pooled connection only when a statement actually runs.
- Context propagation into
@Async methods, so traces follow work onto other threads.
It also removed the deprecated layertools jar mode and deprecated Derby support.
35. Which Spring Boot version should a new service use today?
Boot 4.1 on Java 21 or 25. Boot 4 still requires only Java 17, but virtual threads need 21 and the AOT cache needs 25. According to Spring's support table, 4.1 gets open-source fixes until July 31, 2027 and 4.0 until December 31, 2026.
Free support for 3.5 ended on June 30, 2026. Fixes for 3.5 now need a commercial subscription.
A new minor arrives about every six months: 4.0 in November 2025, 4.1 in June 2026, 4.2 due in November. A team that stays within one minor of current never faces a two-year jump.