Skip to content

v1.4.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 20 Sep 16:48
· 11 commits to main since this release
v1.4.2
309cddb

[1.4.2] — 2026-09-20

A rejection of an unknown method is no longer a riddle. Previously a client got a "method not found" code whose message was the method name itself — there was no way to tell from it whether the server keeps working and what to do next. The response now names the unsupported method, lists the protocol methods the server does answer, and states that the connection stays open.

Context. Some clients send their own requests that the protocol does not define — sometimes right after the connection is established, before the ready notification. The server rejects them and carries on, but the old rejection looked like a breakage: one word with the method name and nothing else. Whoever reported such a case spent hours tracking down the cause.

Changed

  • The rejection text for an unsupported method. The response code is the same, "method not found" (-32601). The message now carries the method name, the list of protocol methods the server answers (initialize, notifications/initialized, tools/list, tools/call), and a note that the connection keeps working. The same list arrives in the data field — it can be parsed without reading the text.
  • A warning with the method name goes to the server log — it shows which request arrived and from which client to expect a repeat.

Compatibility

  • Protocol behaviour is unchanged: same response code, the connection stays alive as before.
  • The connection drop on an outside request sent before the ready notification was a separate defect of the protocol library, fixed in 1.2.4 along with its upgrade. It is not affected here.

Verification

  • cargo test --workspace --all-features: 928 passed, 0 failed. cargo fmt --all and cargo clippy --all-targets --all-features -- -D warnings: clean.
  • Live check against the installed server: a four-message exchange — connect, outside request, ready notification, tool list request. The outside request gets the new rejection text, the connection is not dropped, and the tool list arrives right after.
  • Releases 1.2.2 and 1.2.3 drop the connection on the same exchange, 1.2.4 and later do not. Checked against the published builds of those releases, not against sources.

Russian version of the changelog: CHANGELOG.md.

Full Changelog: v1.4.1...v1.4.2

Assets 8
Loading