Skip to content

Conversation

@Nyholm
Copy link
Contributor

@Nyholm Nyholm commented Dec 27, 2025

Motivation and Context

This will just make the API more strict. It allows us add parameters to these methods without breaking BC.

How Has This Been Tested?

I did not test it

Breaking Changes

Yes, this is a breaking change and should be merged when preparing for 0.3.0

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

@Nyholm Nyholm added the BC Break Breaking the Backwards Compatibility Promise label Dec 27, 2025
@Nyholm Nyholm added this to the 0.3.0 milestone Dec 27, 2025
Copy link
Member

@chr-hertel chr-hertel left a comment

Choose a reason for hiding this comment

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

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BC Break Breaking the Backwards Compatibility Promise Status: Reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants