Skip to content

chore(core): regenerate 2026-07-28 spec reference types at spec commit 77cb2648#2259

Closed
felixweinberger wants to merge 2 commits into
mainfrom
fweinberger/spec-types-regen-0168c57f
Closed

chore(core): regenerate 2026-07-28 spec reference types at spec commit 77cb2648#2259
felixweinberger wants to merge 2 commits into
mainfrom
fweinberger/spec-types-regen-0168c57f

Conversation

@felixweinberger

Copy link
Copy Markdown
Contributor

Refreshes the generated 2026-07-28 spec reference types to the current draft
schema and extends the spec-comparison test to cover a newly named params
interface.

Motivation and Context

#2252 vendored the 2026-07-28 reference types from a slightly older draft-spec
commit. Regenerating at the current draft schema (last touched by
77cb2648) picks up three changes that landed since:

  • DiscoverResult now extends CacheableResult
  • extension capability keys document the mandatory _meta-style prefix rule
  • ElicitationCompleteNotificationParams is extracted as a named interface

The third change adds a named type the SDK already has a zod-inferred
counterpart for, so the comparison test promotes it from the missing-types
list to a compatibility check. The DiscoverResult escape entry's note now
also names the new ttlMs/cacheScope mismatch (owned by the SEP-2549 PR).

How Has This Been Tested?

  • pnpm test:all, pnpm typecheck:all, pnpm lint:all, pnpm build:all green
  • Both spec comparison tests pass; deliberately narrowing an SDK schema type
    fails typecheck through the comparison tests in both directions, confirming
    the guards are live
  • Conformance suites (client + server) unchanged against the expected-failures
    baselines

Breaking Changes

None — generated reference types and tests only; no runtime code changes.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Generated with scripts/fetch-spec-types.ts. The recorded commit
(77cb2648) is the latest one touching schema/draft/schema.ts, matching
what the scheduled spec-types refresh would stamp — so the nightly job sees
this as current. No changeset: generated reference types and test files only,
no published-package behavior change.

…t 77cb2648

Picks up three draft-schema changes since the previous generation:
DiscoverResult now extends CacheableResult, extension capability keys
document the mandatory _meta-style prefix rule, and
ElicitationCompleteNotificationParams is extracted as a named interface.

The recorded commit is the latest one touching schema/draft/schema.ts,
matching what the scheduled spec-types refresh would stamp.
…7-28 spec comparison

The regenerated schema extracts the elicitation-complete notification
params as a named interface; the SDK already exports the matching
zod-inferred type, so it gets a compatibility check instead of a
MISSING_SDK_TYPES entry.

Also notes the new CacheableResult mismatch (required ttlMs/cacheScope)
on the DiscoverResult escape entry, owned by the SEP-2549 PR.
@felixweinberger felixweinberger requested a review from a team as a code owner June 8, 2026 18:33
@changeset-bot

changeset-bot Bot commented Jun 8, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 296908a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@felixweinberger felixweinberger deleted the fweinberger/spec-types-regen-0168c57f branch June 8, 2026 18:34
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.

1 participant