Spring AI 2.0.0-M6: Observability and API Cleanup
Spring AI 2.0.0-M6 was released on May 8, 2026, alongside maintenance updates to the 1.0.x (1.0.7) and 1.1.x (1.1.6) lines. M6 is a significant milestone-before-GA release that tightens the API surface and expands observability support throughout the framework.
The most consequential breaking change is the removal of PromptChatMemoryAdvisor. Teams that relied on this advisor for multi-turn conversation memory must now provide explicit conversation IDs, which aligns with how production chat applications typically manage session state. This change makes the memory lifecycle explicit rather than implicit, reducing unexpected state leakage in concurrent scenarios. The M6 release also removes setter methods from OpenAI, Mistral, and MiniMax options classes, pushing those types toward immutable configuration patterns consistent with Spring Framework 7's general direction.
Observability coverage has expanded: chat model invocations and tool/function calls now emit structured spans and metrics that integrate directly with OpenTelemetry-compatible backends. Combined with Spring Framework 7's native OTel trace propagation, this means a complete trace from HTTP request through AI tool call can be assembled without custom instrumentation. A new buildRequestPrompt default method on the ChatModel interface further standardizes how models convert structured requests to prompt strings.
Two vector store integrations were removed in M6: SAP HANA DB and Infinispan. Teams relying on these integrations should plan a migration before the 2.0.0 GA release. Additionally, OpenAiConnectionProperties has been renamed to OpenAiCommonProperties — a minor but breaking rename that will require configuration file updates. Overall, M6 signals that the Spring AI team is stabilizing the 2.0 API surface, and a GA release is expected in the coming months.
IntelliJ IDEA 2025.3.5 Fixes Spring Bean Search Performance
JetBrains released IntelliJ IDEA 2025.3.5 in May 2026 with a focused fix for Spring Framework users who have not yet migrated from the 2025.3.x track. The primary change prevents "searches for declared Spring beans" from being triggered during typing or code completion — a background operation that was firing unnecessarily on each keystroke in Spring-heavy projects.
For teams working on large Spring Boot codebases with hundreds or thousands of beans, this regression caused noticeable UI stuttering and delayed autocompletion. The fix ensures that bean discovery is only performed when explicitly needed rather than eagerly on every editor event. Spring developers on the 2025.3.x line who have experienced sluggish editor performance should update promptly.
The update is available through the IDE's built-in updater, the JetBrains Toolbox App, Ubuntu snaps, or direct download. Developers who have already migrated to IntelliJ IDEA 2026.1 are not affected, as that release carried a redesigned indexing architecture.
Read more — JetBrains Blog
Links & Sources
You May Also Enjoy
