Skip to content

Conversation

dickhardt
Copy link

Added instruction to update version in the publish process.

Motivation and Context

How Has This Been Tested?

Breaking 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

Added instruction to update version in the publish process.
rdimitrov
rdimitrov previously approved these changes Sep 12, 2025
@@ -143,6 +143,7 @@ Add an `mcpName` field to your `package.json`:
### How It Works
- Registry fetches `https://registry.npmjs.org/your-npm-package`
- Checks that `mcpName` field matches your server name
- Update the version to be the version of your published npm package
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably live in instructions, or maybe in the 'example server.json' section - not the description of how the validation mechanism works

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not find the "instructions" -- this is what was in front of me while I was using the software.
Updated to align with validation mechanism, since it is part of the validation which was why my server was not being published and I got an error.

Copy link
Member

@domdomegg domdomegg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As above

Updated instructions to clarify version check.
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