Remove ExperimentalAttribute from official Extensions/Tasks/MRTR APIs and align MCPEXP001 usage#1642
Open
Copilot wants to merge 3 commits into
Open
Remove ExperimentalAttribute from official Extensions/Tasks/MRTR APIs and align MCPEXP001 usage#1642Copilot wants to merge 3 commits into
ExperimentalAttribute from official Extensions/Tasks/MRTR APIs and align MCPEXP001 usage#1642Copilot wants to merge 3 commits into
Conversation
Co-authored-by: PranavSenthilnathan <12225508+PranavSenthilnathan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Remove experimental attribute for official APIs
Remove Jun 11, 2026
ExperimentalAttribute from official Extensions/Tasks/MRTR APIs
Contributor
|
@copilot You can remove the unused fields (MRTR, Tasks, Extensions) from /src/Common/Experimentals.cs. We should still use |
Co-authored-by: PranavSenthilnathan <12225508+PranavSenthilnathan@users.noreply.github.com>
Contributor
Author
Implemented in
|
Copilot
AI
changed the title
Remove
Remove Jun 11, 2026
ExperimentalAttribute from official Extensions/Tasks/MRTR APIsExperimentalAttribute from official Extensions/Tasks/MRTR APIs and align MCPEXP001 usage
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.
Extensions, Tasks, and MRTR are now official protocol surfaces and should no longer emit experimental API diagnostics. This change removes
ExperimentalAttributefrom those public APIs and updates howMCPEXP001is represented for future experimental spec features.API annotation cleanup (official surfaces)
[Experimental(...)]from official Extensions/Tasks/MRTR types and members inModelContextProtocol.Core, including:InputRequest,InputResponse,InputRequiredResult,InputRequiredException)RequestParams.InputResponses,RequestParams.RequestState)ClientCapabilities.Extensions,ServerCapabilities.Extensions)IMcpTaskStore,InMemoryMcpTaskStore,McpTaskInfo,InputResponseReceivedEventArgs,McpServer.CreateMcpTaskScope,McpServer.IsMrtrSupported)System.Diagnostics.CodeAnalysisimports in touched files.Diagnostic ID policy update
src/Common/Experimentals.cs.MCPEXP001constant for experimental MCP specification features (SpecificationFeature_DiagnosticId) with guidance comments indicating new experimental spec features should add feature-specific message/URL constants using this ID.MCPEXP001is used for experimental MCP specification features going forward.Regression coverage
ExperimentalAttribute.