Bump rmcp past the explicit V_2026_07_28 pin #16
Labels
No labels
deferred
waiting-on-julian
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jlxq0/typst-mcp#16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.LATESTstill points at 2025-11-25, which is why the pin is written out rather than inherited.Plan.mdrecorded 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 (_metawith the protocol version and client capabilities, plusMcp-Protocol-Version/Mcp-Method/Mcp-Nameheaders on streamable-HTTP POSTs) is pinned bytests/mcp.rs, so a bump that breaks it will be caught by the gate.Plan.md's wording: "Bumping
rmcppast the explicitV_2026_07_28pin once upstream PR #1105 lands."