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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Problem:
kotlinlang-mcp-serveris missing from thematrix.samplelists in both.github/workflows/samples.ymland.github/workflows/build.yml(each lists onlykotlin-mcp-client,kotlin-mcp-server,simple-streamable-server,weather-stdio-server). No CI job ever compiles or tests this sample, so every green check on this PR covers code the PR does not touch, and the one line it does change is unverified.Failure scenario: the Ktor 3.5.2 → 3.6.0 minor touches ContentNegotiation (
Acceptentries withq=0are now rejected), auth, and SSE. If it breaks compilation or the Streamable HTTP endpoint in this sample, this PR still merges green and the breakage surfaces only when someone clones the sample — the same blind spot the ~20 earlier dependency bumps to this directory landed through.Suggested fix: add
- kotlinlang-mcp-serverto thematrix.samplelist in.github/workflows/samples.ymland.github/workflows/build.yml(a follow-up PR is fine — the sample's unit tests use mocked HTTP clients andMapApplicationConfig, so no Algolia secrets are needed for./gradlew build). Until that lands, run./gradlew buildinsamples/kotlinlang-mcp-serverlocally before merging this bump.Non-blocking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verification update on the local-build advice above: I ran
./gradlew buildinsamples/kotlinlang-mcp-serveragainst bothktor = "3.5.2"andktor = "3.6.0"(JDK 21 toolchain).The bump itself is clean. Compiles,
installDistworks, the server boots, and a live Streamable HTTP smoke test over Ktor 3.6.0 passes:initialize→ 200 +mcp-session-id,notifications/initialized→ 202,tools/listreturns both tools, and theGET /mcpSSE stream opens withtext/event-stream. The CORS + ContentNegotiation + SSE + Netty combination this sample uses is unaffected by the 3.6.0 changes.But the build is red for an unrelated, pre-existing reason — worth knowing before you act on a
BUILD FAILED:55/56 tests pass; this one fails identically on
3.5.2, so it is not caused by this PR. The path involves no Ktor at all — it isChannelTransport.createLinkedPair()+Client.connect()underrunTest, where the SDK's 60 s initialize timeout fires immediately in virtual time.Suggested handling: merge this bump on its own merits, and track the
KotlinlangServerTestinitialize timeout as a separate issue (alongside addingkotlinlang-mcp-serverto the CI matrices, which is why neither problem was visible here).Produced by Air Automations. Name: Code review / Run: https://air.jetbrains.cloud/org/05cf1a7f-6ab5-713b-abd3-29d0c8a05e2d/automations/409567ec-d3a7-40ac-ba95-8518ec577ac2?run=0a8d01a9-719b-4c78-a279-9fa66a41b229