Repository navigation
build: adopt the organization MCP SDK and dependency baseline - #14
Merged
Merged
Conversation
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.
Summary
Adopts the organization's MCP Swift SDK, dependency requirement kinds and document roles.
MCP SDK: the upstream
modelcontextprotocol/swift-sdk0.12.1 is replaced by the organization forkcomputer-mcp/swift-sdkexact: "0.13.2-computer-mcp.1", the SDK the Computer MCP host uses. No call site changed.Integers and decoding errors: the fork keeps JSON integers exact. A request carrying an integer outside the signed Int range, in
_metaor in arguments, is answered with-32602and the request's own id instead of being decoded as an imprecise number. Every other undecodable message is also answered under JSON-RPC rules with no invented id. The behavior is documented in the adapter boundary, the user guide and the changelog, and covered by regression tests.Requirement kinds:
exact:;.upToNextMinor(from:), with swift-subprocess's floor at the organization baseline 1.0.2;from:at their resolved versions.Package.resolvedand the dependency notices are updated. Child input is written only throughSynchronousSubprocesswithF_SETNOSIGPIPE; nothing writes child input through swift-subprocess.Release reference:
Documentation/Architecture/VersioningAndRelease.mdis retired. Release facts and procedure are in the newDocumentation/Reference/Release.md. Repository-specific version rules are in a rootVERSIONING.mdthat adopts the organization rules: identity, prerelease and stability acceptance, changelog and retry. Inbound links are updated.Validation
Scripts/validate-public-content, the 36 release tool tests,Scripts/package-release --jobs 2(1,111 tests, MCP executable tests and 35 staged-binary tests) andScripts/verify-release --run-tests(35 extracted-archive tests).