Skip to content

Sync enable-2026-07-28 with upstream main (#1012, #1008/SEP-2549, #1014) - #1

Merged
sylvansys merged 4 commits into
enable-2026-07-28from
update-enable-2026-07-28
Jun 19, 2026
Merged

Sync enable-2026-07-28 with upstream main (#1012, #1008/SEP-2549, #1014)#1
sylvansys merged 4 commits into
enable-2026-07-28from
update-enable-2026-07-28

Conversation

@sylvansys

Copy link
Copy Markdown

Brings the fork's enable-2026-07-28 branch up to date with modelcontextprotocol/go-sdk@main by merging upstream forward (non-destructive — no history rewrite). The branch was 3 commits behind upstream (last synced at d9728a8, 2026-06-16; upstream now at b85574f, 2026-06-18).

What this pulls in

Our patch is untouched

The single-commit enable patch (19527b6, adds protocolVersion20260728 = "2026-07-28" to supportedProtocolVersions in mcp/shared.go) is preserved verbatim — mcp/shared.go blob is byte-identical (ef24b40d) before and after, and none of the 3 upstream commits touch that file, so the merge is conflict-free. The net diff vs the old branch tip is exactly the 3 upstream commits' files.

Why still needed

Upstream main still lists only up to 2025-11-25 in supportedProtocolVersions (2026-06-30 is defined-but-unlisted; 2026-07-28 is absent entirely), and the config-knob PR modelcontextprotocol#947 (ServerOptions.SupportedVersions) remains open. So the fork + the go.mod replace in constellos/mcp stay load-bearing.

After merge, services/mcp/go.mod will re-point its replace at the new branch tip.

guglielmo-san and others added 4 commits June 17, 2026 11:41
…ocol#1014)

To guarantee a better compatibility with legacy server, enable the
fallback to the legacy initialize rpc in case of any error returned by
the server, in case of `server/discover` request.
@sylvansys
sylvansys merged commit c4bf1d6 into enable-2026-07-28 Jun 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants