Bump rmcp past the explicit V_2026_07_28 pin #16

Open
opened 2026-08-26 04:49:56 +00:00 by jlxq0 · 0 comments
Owner

Migrated from Plan.md's "Deferred (do not drift into these)" section when that file was retired; open work belongs in issues, not in a file with no state. Nothing here is scheduled and no decision has been taken. Do not start it without an explicit go.

The protocol version is pinned explicitly to V_2026_07_28. LATEST still points at 2025-11-25, which is why the pin is written out rather than inherited.

Plan.md recorded the unblocking condition as upstream rmcp PR #1105 landing. Verify that upstream state before acting on it — it was written on 2026-08-19 and nobody has rechecked it since. The working request shape for 2026-07-28 (_meta with the protocol version and client capabilities, plus Mcp-Protocol-Version / Mcp-Method / Mcp-Name headers on streamable-HTTP POSTs) is pinned by tests/mcp.rs, so a bump that breaks it will be caught by the gate.

Plan.md's wording: "Bumping rmcp past the explicit V_2026_07_28 pin once upstream PR #1105 lands."

Migrated from `Plan.md`'s "Deferred (do not drift into these)" section when that file was retired; open work belongs in issues, not in a file with no state. **Nothing here is scheduled and no decision has been taken.** Do not start it without an explicit go. The protocol version is pinned explicitly to `V_2026_07_28`. `LATEST` still points at 2025-11-25, which is why the pin is written out rather than inherited. `Plan.md` recorded the unblocking condition as upstream rmcp PR #1105 landing. **Verify that upstream state before acting on it — it was written on 2026-08-19 and nobody has rechecked it since.** The working request shape for 2026-07-28 (`_meta` with the protocol version and client capabilities, plus `Mcp-Protocol-Version` / `Mcp-Method` / `Mcp-Name` headers on streamable-HTTP POSTs) is pinned by `tests/mcp.rs`, so a bump that breaks it will be caught by the gate. Plan.md's wording: "Bumping `rmcp` past the explicit `V_2026_07_28` pin once upstream PR #1105 lands."
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jlxq0/typst-mcp#16
No description provided.