-
Notifications
You must be signed in to change notification settings - Fork 5
Update spec to 2025-03-26 #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…rt/authorization/batching support
PR HealthChangelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs. |
pkgs/dart_mcp/lib/src/api/api.dart
Outdated
static const oldestSupportedVersion = ProtocolVersion.v2024_11_05; | ||
|
||
/// The most recent version supported by the current API. | ||
static const latest = ProtocolVersion.v2025_03_26; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be a values.last
so that we do not have to update it? Or is making this fixed intentional so that we can work on supporting a protocol version before we set it to this latest field?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do see in the future us adding additional "known" but unsupported protocols here. Basically, when a new version gets released we can add the entry so that we can parse it etc and compare it.
I think I will rename this to latestSupported
?
…sion to oldestSupported
I had already implemented one portion of this by accident apparently (completions support).
Adds version negotiation and a few other small breaking changes since I wanted to make a breaking change anyways to convert the protocol version to an enum.