Spring AI 2.1.0 GA: MCP 2026-07-28, Sessions, and Safer Tool Calling

Spring AI 2.1.0 reached general availability on November 20, together with 2.0.3. It requires Spring Boot 4.2 and includes more than 430 commits from 86 contributors since 2.0.0. The milestones introduced most of these features. This GA release makes them the supported baseline.

The headline features:

  • MCP 2026-07-28 support through MCP Java SDK 2.2.0. Turn on the stateless "modern" server mode with spring.ai.mcp.server.protocol=MODERN.
  • DecisionModel API, which gives classification, routing and LLM-as-judge calls a typed contract. Implementations ship for OpenAI, Ollama and System One.
  • Message parts such as ReasoningPart and ToolCallPart, with OpenAI Responses API support enabled through spring.ai.openai.chat.api=responses.
  • Session API, which replaces ChatMemory. ChatMemory is now deprecated and will be removed in 3.0.0.

Tool calling now has stricter defaults. A tool can require human confirmation with requiresConfirmation = true, and tool calls are limited to 40 per tool and 150 per turn by default. That limit can cut off long agent loops that previously ran unbounded. The release fixes 13 CVEs, and 2.0.3 carries the same fixes for teams that can't move to Boot 4.2 yet.

Read more — Spring Blog


Spring Cloud 2026.0.0 "Paddington" Released on Spring Boot 4.2

The Spring Cloud 2026.0.0 release train, codenamed Paddington, is out and is built on Spring Boot 4.2.0. Its modules are at version 5.1.0. Spring Cloud Bus is no longer a separate project. It now lives inside Spring Cloud Stream, and its Maven coordinates are unchanged.

The release fixes a long list of CVEs: CVE-2026-59425 through 59428 in Gateway, 59433 in Netflix, 59434 in Kubernetes, 59435 through 59437 in Config, 59439 and 59440 in Function, and 59441 in Stream. Dependencies move to Resilience4J 2.4.0, Feign 13.14, Fabric8 8.0.0 and Spring Vault 4.1.0. The reactive Kafka binder, Schema Registry, and Spring Cloud Function's RSocket and gRPC modules are deprecated. Teams that use them should plan to migrate.

For the 2025.1 line, Spring Cloud 2025.1.5 (Oakwood) shipped the same day as a maintenance release.

Read more — Spring Blog


Spring Batch 6.1 GA: @JobParameter, PageableItemReader, and Breaking DAO Changes

Spring Batch 6.1 is generally available. It is built on Spring Framework 7.1.0, Spring Integration 7.2.0, Spring Data 2026.1.0 and Micrometer 1.18.0. New features:

  • A @JobParameter annotation, which replaces the @Value SpEL expressions over jobParameters.
  • A new PageableItemReader.
  • Location patterns in MultiResourceItemReaderBuilder.
  • A configurable collection prefix for the MongoDB job repository (the default is BATCH_).
  • A library-agnostic JsonLineMapper that works with Jackson or Gson, plus a new JsonLineAggregator.

There are breaking changes. The JDBC DAOs lose their no-argument constructors in favour of JdbcClient. The staged builder DSL has changed. Avro readers now enforce trusted classes. AsyncItemProcessor, AsyncItemWriter and ChunkTaskExecutorItemWriter moved into spring-batch-core. On the performance side, the release runs fewer repository queries on restarts and partitioned steps and uses less memory.

Read more — Spring Blog


Spring Boot 4.1.3 and 4.0.10 Patch Releases

On November 20, the Spring team shipped Spring Boot 4.1.3, with 112 bug fixes, documentation improvements and dependency upgrades, and Spring Boot 4.0.10 for the 4.0 line. Both are available from Maven Central.

These releases came out the same week as the Java4Shell OpenJDK vulnerability (CVE-2026-114938). That fix lives in the JDK, not in Spring Boot. So after upgrading Boot, also rebuild your container images on a patched JDK (17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1).

Read more — Spring Blog