Skip to content

Conversation

@richarda23
Copy link

Motivation and Context

Fixes issue #1201 - renaming 'validation' folder to 'validators'

How Has This Been Tested?

No, I just ran tests + linting

Breaking Changes

Yes - if users were importing validators from 'validation' package, the import path will now be different

Types of changes

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

Checklist

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

Additional context

@richarda23 richarda23 requested a review from a team as a code owner December 27, 2025 11:20
@changeset-bot
Copy link

changeset-bot bot commented Dec 27, 2025

⚠️ No Changeset found

Latest commit: d71388b

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.

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

@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 27, 2025

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/client@1340
npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/server@1340

commit: d71388b

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