Skip to content

Conversation

@LucaButBoring
Copy link
Contributor

Sets 2025-11-25 as the latest supported client version.

Motivation and Context

Upgrades the declared version to avoid any possible issues as we actually implement the latest protocol version's features.

How Has This Been Tested?

Unit tests.

Breaking Changes

None, version negotiation should handle differences in supported version ranges.

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

Allows "priming" events for new SSE streams, which the TS SDK has implemented on the latest protocol version (per SEP-1699).
@LucaButBoring LucaButBoring force-pushed the feat/2025-11-25-is-the-latest-protocol-version-btw branch from 96c92f4 to 4517a23 Compare January 23, 2026 00:53
if (data == null || data.isBlank()) {
logger.debug("Skipping SSE event with empty data (stream primer)");
return Flux.empty();
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice fix

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