Repository navigation
docs(specs): 058 revision — mcp-go v1.0.0-beta.1 clears the 2026-07-28 gate - #1033
Merged
Merged
Conversation
…7-28 gate Related #532 Dependency gate cleared 2026-08-12: mcp-go v1.0.0-beta.1 (mark3labs/mcp-go#951) ships full 2026-07-28 support with per-request era detection. ## Changes - Dependency Gate section rewritten as CLEARED (pin corrected v0.54.0 -> v0.57.0); merge constraint: no beta pin on main without v1.0.0 stable or the FR-028 legacy pin - Error codes updated to the final renumbering: FR-008 -32001 -> -32020 (HEADER_MISMATCH), FR-006 cites -32022 (UNSUPPORTED_PROTOCOL_VERSION); FR-018 -32602 mapping verified against beta.1 (-32002 legacy-era only) - Scope note: FR-001..006 / FR-014..016 recast as adopt-and-verify (library provides era detection, server/discover, GET/DELETE handling, MRTR, legacy conformance) - Cross-Spec Reconciliation: Spec-057 Option A/B decision is now the mandatory first task; acceptance = the 2 tests failing under beta.1; ~21-call-site ClientSessionFromContext audit flagged - New FR-028: pin client-facing transport legacy-only via WithStreamableHTTPProtocolVersions(LegacyProtocolVersions()...) as the safe merge state - 'RC may shift' assumption resolved (spec FINAL 2026-07-28); new Risks & Watch Items section (OAuth authorization-hardening churn, frozen goldens, JSON Schema 2020-12)
Deploying mcpproxy-docs with
|
| Latest commit: |
4e1babf
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b982978f.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://docs-spec-058-gate-cleared.mcpproxy-docs.pages.dev |
Related #532 Review round 1 (P2): the gate paragraph said synthesized legacy session state keeps ClientSessionFromContext handlers working, contradicting the Reconciliation section where session-id-dependent set_profile fails. Qualified: handlers receive a session object, but no persistent session id is bound.
Contributor
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 32974997919 --repo smart-mcp-proxy/mcpproxy-go
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
github-actions Bot
pushed a commit
that referenced
this pull request
Aug 25, 2026
…specs 101/102 tracked (#1041) - release-qa-gate-playwright (T2): in_review -> done, pr #1030 (advisory Playwright web-UI sweep merged into the release gate). - mcp-2026-upgrade: blocked -> in_progress. The mcp-go gate cleared with v1.0.0-beta.1 (2026-08-12); spec 058 revision in review as #1033. Note rewritten: the remaining blocker is the Spec 057 cross-spec conflict, not the dependency. - tpa-db: todo -> in_review with spec: specs/101-tpa-db and pr #1028 (spec stage only; all three child tasks stay todo). - New epic schema-deferred (P1, spec 102, in_progress): deferred-schema serialization for the direct tools/list surface, spec merged in #1035 (issue #971), plan in progress. Reconnect-backoff work (#1014/#1039/#1040) is deliberately not added — the roadmap never tracked it; git history does. ROADMAP.md regenerated; gen-roadmap.py --check passes.
Both found by cross-model review and verified against the beta.1 module cache. - The scope note listed FR-015/FR-016 as "adopt-and-verify" on the strength of "MRTR bridging" in mcp-go v1.0.0-beta.1. The library ships MRTR *participation*, not *bridging*: a server can raise an input_required result (mcp.NewInputRequiredResult, MultiRoundTripResult embedded in CallToolResult / GetPromptResult / ReadResourceResult) and a client can answer one locally (client/mrtr.go gathers responses from handlers and re-sends with the echoed requestState). A proxy must do neither - relay outward without answering, then carry inputResponses back upstream under a new request id. Nothing in beta.1 does that, and requestState is opaque and upstream-scoped, so whether it can be forwarded verbatim is an open plan-time question. FR-015/FR-016 moved to the mcpproxy-specific list. - Risks & Watch Items said CallToolResult gains resultType / ttlMs / cacheScope. It gains resultType (embedded mcp.Result) and the MRTR fields, but ttlMs and cacheScope live on mcp.CacheableResult, which is embedded only by PaginatedResult, ReadResourceResult and DiscoverResult - which is exactly FR-019's "list/read responses" scope, so FR-019 itself was right. Everything else in the revision checked out against the module and the repo: v1.0.0-beta.1 exists and v0.58.0 is the latest v0.x; the pin really is v0.57.0; server/streamable_http_modern.go carries the 2026-07-28 era detection; WithCacheHints/WithMethodCacheHints exist at server/server.go:254,267; the error renumbering is real (HEADER_MISMATCH -32020, MISSING_REQUIRED_CLIENT_CAPABILITY -32021, UNSUPPORTED_PROTOCOL_VERSION -32022, with -32020..-32099 reserved); and server/resource_errors.go returns INVALID_PARAMS on the modern era and RESOURCE_NOT_FOUND on the legacy one, as FR-018 describes. The compile probe was re-run rather than trusted: on main @ 4d30624 with the beta.1 pin, both editions build, go vet is clean, and TestProfile_ produces exactly the two named failures. That result is now recorded inline.
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
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.
Revises spec 058 now that the dependency gate for #532 has cleared: mcp-go v1.0.0-beta.1 (2026-08-12, mark3labs/mcp-go#951) ships full 2026-07-28 support with per-request era detection.
Encodes the final error-code renumbering (-32020/-32021/-32022), recasts FR-001..006 / FR-014..016 as adopt-and-verify, makes the Spec-057 Option A/B decision the mandatory first task (acceptance = the 2 tests failing under beta.1), and adds FR-028 (legacy-only transport pin as the safe merge state) plus a Risks & Watch Items section.
Related #532 — spec-only change, no code touched.