Repository navigation
Release Platform packages - #19
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@codelitdev/mcp-server-kit@0.5.0
Minor Changes
ffcabaa: Serve MCP 2026-07-28. The kit now runs on the official MCP TypeScript SDK 2 (
@modelcontextprotocol/server) and is stateless: every request is authenticated, resolved to the product context, and handled by a fresh request-local server.server/discover, per-request protocol envelopes,Mcp-Method/Mcp-Nameheader validation,resultType, and cache hints ontools/listandserver/discover(five minutes, private by default; setcatalogCacheHintto change it).initializeno longer mints anMcp-Session-Id;GETandDELETEanswer405.structuredContentplus onetextcopy. The invalid{ type: "json" }content item is gone; strict clients such as ChatGPT rejected every result carrying it and retried, duplicating writes.confirm: true, are tool results withisError: trueandstructuredContent: { code, message, details }, returned with HTTP 200. They were JSON-RPC errors with string codes, which JSON-RPC does not allow. Authentication and context failures before dispatch return the platform error body ({ code, message }) with its HTTP status.$schema, so clients read them under MCP's default dialect. Annotations follow the spec (readOnlyHint,destructiveHint); the risk stays in the tool's_meta.risk.description,instructions,catalogCacheHint.createMcpSessionStore,McpSession,McpSessionStore,StreamableHTTPServerTransport,WebStandardStreamableHTTPServerTransport, and the kit'ssessionsproperty.platform-conformancereads MCP tool failures fromisErrortool results.Patch Changes
@codelitdev/platform@0.5.0
Patch Changes
@codelitdev/platform-conformance@0.5.0
Patch Changes
ffcabaa: Serve MCP 2026-07-28. The kit now runs on the official MCP TypeScript SDK 2 (
@modelcontextprotocol/server) and is stateless: every request is authenticated, resolved to the product context, and handled by a fresh request-local server.server/discover, per-request protocol envelopes,Mcp-Method/Mcp-Nameheader validation,resultType, and cache hints ontools/listandserver/discover(five minutes, private by default; setcatalogCacheHintto change it).initializeno longer mints anMcp-Session-Id;GETandDELETEanswer405.structuredContentplus onetextcopy. The invalid{ type: "json" }content item is gone; strict clients such as ChatGPT rejected every result carrying it and retried, duplicating writes.confirm: true, are tool results withisError: trueandstructuredContent: { code, message, details }, returned with HTTP 200. They were JSON-RPC errors with string codes, which JSON-RPC does not allow. Authentication and context failures before dispatch return the platform error body ({ code, message }) with its HTTP status.$schema, so clients read them under MCP's default dialect. Annotations follow the spec (readOnlyHint,destructiveHint); the risk stays in the tool's_meta.risk.description,instructions,catalogCacheHint.createMcpSessionStore,McpSession,McpSessionStore,StreamableHTTPServerTransport,WebStandardStreamableHTTPServerTransport, and the kit'ssessionsproperty.platform-conformancereads MCP tool failures fromisErrortool results.@codelitdev/platform@0.5.0
@codelitdev/billing@0.5.0
No changes in this release.
@codelitdev/design-system@0.5.0
No changes in this release.
@codelitdev/oauth-server-kit@0.5.0
No changes in this release.
@codelitdev/observability@0.5.0
No changes in this release.
@codelitdev/platform-cli@0.5.0
No changes in this release.