Repository navigation
Conversation
spring-ai-mcp 2.0.1 still requires io.modelcontextprotocol.sdk:mcp:2.0.0, so no other dependency version changes with this upgrade. The removed dependencyManagement entry pinned only mcp-core, one of the three MCP SDK artifacts (mcp, mcp-core, mcp-json-jackson3). It could not control the SDK as a whole and would have left a half-upgraded SDK behind the next Spring AI bump, so Spring AI now owns the SDK version entirely. Verified locally: the *-mcp module tests pass and the resolved SDK stays at 2.0.0. Co-authored-by: DeepSeek V4.1 Flash <noreply@deepseek.com>
springdoc-openapi-starter-common-mcp declares spring-ai-mcp with compile scope, which transitively provides spring-ai-model and the MCP SDK. The note still described spring-ai-model plus optional mcp-core and spring-ai-mcp, which no longer matches the pom. The WebFlux module also declares io.micrometer:context-propagation, used to register the MDC ThreadLocalAccessor with the Micrometer ContextRegistry. Co-authored-by: DeepSeek V4.1 Flash <noreply@deepseek.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
spring-ai.versionfrom 2.0.0 to 2.0.1.mcp-sdk.versionproperty and theio.modelcontextprotocol.sdk:mcp-coredependencyManagement entry.Why the MCP SDK pin goes away
spring-ai-mcpdeclaresio.modelcontextprotocol.sdk:mcp(compile, non-optional), which brings inmcp-coreandmcp-json-jackson3. Spring AI 2.0.1 still requiresmcp:2.0.0, so the removed entry - which pinned onlymcp-core, one of the three artifacts - was a no-op that could not control the SDK as a whole and would have left a half-upgraded SDK behind the next Spring AI bump.Verification
mvn -o -Dskip.npm=true -pl springdoc-openapi-starter-common-mcp,springdoc-openapi-starter-webmvc-mcp,springdoc-openapi-starter-webflux-mcp -am test-> BUILD SUCCESS (Maven 3.9.16, JDK 25)MCP tests green: 32 (common-mcp) + 22 (webmvc-mcp) + 17 (webflux-mcp); upstream modules 55 + 653 + 136.
dependency:tree -Dincludes=io.modelcontextprotocol.sdkstill resolvesmcp:2.0.0,mcp-json-jackson3:2.0.0,mcp-core:2.0.0.A second commit aligns the dependency notes in
springdoc-openapi-starter-common-mcp/README.mdwith the poms