Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@felixweinberger
Copy link
Collaborator

@felixweinberger felixweinberger commented Nov 10, 2025

Motivation and Context

Whenever I ran npm i or git checkout main this diff would be created. So it seems like this was inadvertently omitted from a previous commit.

How Has This Been Tested?

Run npm i

Breaking Changes

None.

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

@pcarleton pcarleton enabled auto-merge (squash) November 11, 2025 13:21
@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 11, 2025

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/conformance/@modelcontextprotocol/conformance@13

commit: 9110ccc

@pcarleton pcarleton merged commit fa7a0bc into main Nov 11, 2025
7 checks passed
@pcarleton pcarleton deleted the fweinberger/fix-npm-install branch November 11, 2025 13:22
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.

3 participants