fix: correct numeric types in progress notifications#361
Merged
jamadeo merged 2 commits intomodelcontextprotocol:mainfrom Aug 7, 2025
Merged
fix: correct numeric types in progress notifications#361jamadeo merged 2 commits intomodelcontextprotocol:mainfrom
jamadeo merged 2 commits intomodelcontextprotocol:mainfrom
Conversation
The standard specifies that these may be floating-point.
d577bd8 to
fe829bd
Compare
alexhancock
approved these changes
Aug 7, 2025
Merged
takumi-earth
pushed a commit
to earthlings-dev/rmcp
that referenced
this pull request
Jan 27, 2026
…tocol#361) * fix: correct numeric types in progress notifications The standard specifies that these may be floating-point. * fix: regenerate schemas
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The standard says:
https://modelcontextprotocol.io/specification/2025-06-18/basic/utilities/progress#progress-flow
Motivation and Context
Aligns with the standard
How Has This Been Tested?
Ran with a FastMCP server that looks like
Breaking Changes
Yes, this changes they type of a public field of a struct.
Types of changes
Checklist
Additional context