Who contributed to Spring on June 17, 2026?

3 developers shipped this update, including tzolov, quaff, and cppwfs.

What were the notable Spring updates?

Restructure tool calling reference docs, Revise DeepSeekApi, and IntegrationFlowBuilder falls back to outputChannelName.

Jun 17, 2026

$ the-wire · showcase

SPRING-AI DOCS OVERHAUL SHIPS AS INTEGRATION FIXES RACE CONDITIONS

By RepoJournal · Filed 06:04 UTC on June 17, 2026 · About Spring · Composed from the cited sources · methodology

3 people shipped this

tzolov @tzolov 1 cited

quaff @quaff 1 cited

cppwfs @cppwfs 1 cited

Spring AI restructured its entire tool calling documentation around the 2.0 narrative while Spring Integration patched critical concurrency bugs across the platform.

Spring AI completed a major docs reorganization [1] that consolidates scattered tool calling references into three canonical pages (tool-calling-advisor, tool-search-tool, chatmodel-tool-calling) and folds migration guidance into upgrade notes. This lands alongside fixes to DeepSeekApi [2] that correct parameter naming and add missing null safety annotations. On the integration front, the team shipped a fallback mechanism [3] in IntegrationFlowBuilder that creates direct channels when both outputChannel and channelName are unavailable, fixing a configuration gap flagged in production. More critically, Spring Integration tackled a concurrency issue [4] in BaseIntegrationFlowDefinition where REFERENCED_REPLY_PRODUCERS could be accessed simultaneously, converting it to a ConcurrentHashMap and making the reuse check atomic. Spring Integration also fixed a timing race condition [5] in JdbcLockRegistryTests that could yield zero-millisecond differences, and Spring Boot aligned its Prometheus Client dependency with Micrometer [6]. All integration fixes are auto-cherry-picking to 7.0.x and 6.5.x branches.

Action items

→ Review Spring AI tool calling docs changes if you're integrating agents - the new structure is canonical moving forward spring-projects/spring-ai [plan]
→ Test IntegrationFlowBuilder configurations without explicit output channels - fallback behavior changed spring-projects/spring-integration [plan]
→ Pull the concurrency fix from Spring Integration if you use BaseIntegrationFlowDefinition in threaded deployments spring-projects/spring-integration [immediate]

References

[1] Restructure tool calling reference docs ↗ spring-projects/spring-ai
[2] Revise DeepSeekApi ↗ spring-projects/spring-ai
[3] IntegrationFlowBuilder falls back to outputChannelName ↗ spring-projects/spring-integration
[4] GH-11127: Fix race condition in BaseIntegrationFlowDefinition ↗ spring-projects/spring-integration
[5] Fix time race condition in the JdbcLockRegistryTests ↗ spring-projects/spring-integration
[6] Align Prometheus Client dependency with Micrometer ↗ spring-projects/spring-boot