deps(nuget): Bump the nuget-all group with 12 updates#85
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
deps(nuget): Bump the nuget-all group with 12 updates#85dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps coverlet.msbuild from 8.0.0 to 10.0.0 Bumps Markdig from 0.44.0 to 1.1.3 Bumps Microsoft.CodeAnalysis.NetAnalyzers from 10.0.102 to 10.0.203 Bumps Microsoft.Data.Sqlite from 10.0.2 to 10.0.7 Bumps Microsoft.Extensions.Hosting from 10.0.2 to 10.0.7 Bumps Microsoft.ML.OnnxRuntime from 1.23.2 to 1.25.1 Bumps Microsoft.NET.Test.Sdk from 18.0.1 to 18.5.1 Bumps ModelContextProtocol from 0.8.0-preview.1 to 1.2.0 Bumps NUnit from 4.4.0 to 4.5.1 Bumps NUnit.Analyzers from 4.11.2 to 4.12.0 Bumps NUnit3TestAdapter from 6.1.0 to 6.2.0 Bumps YamlDotNet from 16.3.0 to 17.1.0 --- updated-dependencies: - dependency-name: coverlet.msbuild dependency-version: 10.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget-all - dependency-name: Markdig dependency-version: 1.1.3 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget-all - dependency-name: Microsoft.CodeAnalysis.NetAnalyzers dependency-version: 10.0.203 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.Data.Sqlite dependency-version: 10.0.7 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.Extensions.Hosting dependency-version: 10.0.7 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.ML.OnnxRuntime dependency-version: 1.25.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-all - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.5.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-all - dependency-name: ModelContextProtocol dependency-version: 1.2.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget-all - dependency-name: NUnit dependency-version: 4.5.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-all - dependency-name: NUnit.Analyzers dependency-version: 4.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-all - dependency-name: NUnit3TestAdapter dependency-version: 6.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-all - dependency-name: YamlDotNet dependency-version: 17.1.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget-all ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
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.
Updated coverlet.msbuild from 8.0.0 to 10.0.0.
Release notes
Sourced from coverlet.msbuild's releases.
10.0.0
Improvements
--coverlet-file-prefixoption for unique report files #1869Fixed
Maintenance
Diff between 8.0.1 and 10.0.0
8.0.1
Fixed
Improvements
Diff between 8.0.0 and 8.0.1
Commits viewable in compare view.
Updated Markdig from 0.44.0 to 1.1.3.
Release notes
Sourced from Markdig's releases.
1.1.3
Changes
🐛 Bug Fixes
🚀 Enhancements
Full Changelog: 1.1.2...1.1.3
Published with dotnet-releaser
1.1.2
Changes
🐛 Bug Fixes
Full Changelog: 1.1.1...1.1.2
Published with dotnet-releaser
1.1.1
Changes
🐛 Bug Fixes
Full Changelog: 1.1.0...1.1.1
Published with dotnet-releaser
1.1.0
Changes
🚀 Enhancements
🧰 Misc
Full Changelog: 1.0.1...1.1.0
Published with dotnet-releaser
1.0.1
Changes
✨ New Features
🧰 Maintenance
🧰 Misc
Full Changelog: 1.0.0...1.0.1
Published with dotnet-releaser
1.0.0
Changes
✨ New Features
🚀 Enhancements
🧰 Misc
Full Changelog: 1.0.0-preview.1...1.0.0
Published with dotnet-releaser
1.0.0-preview.1
Changes
✨ New Features
🐛 Bug Fixes
🧰 Misc
Full Changelog: 0.45.0...1.0.0-preview.1
Published with dotnet-releaser
0.45.0
Changes
🚀 Enhancements
Full Changelog: 0.44.0...0.45.0
Published with dotnet-releaser
Commits viewable in compare view.
Updated Microsoft.CodeAnalysis.NetAnalyzers from 10.0.102 to 10.0.203.
Release notes
Sourced from Microsoft.CodeAnalysis.NetAnalyzers's releases.
10.0.203
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.203and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.202
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.202and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.201
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.201and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.200
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.200and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.107
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.107and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.106
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.106and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.105
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.105and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.104
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.104and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.103
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.103and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023
Commits viewable in compare view.
Updated Microsoft.Data.Sqlite from 10.0.2 to 10.0.7.
Release notes
Sourced from Microsoft.Data.Sqlite's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Hosting from 10.0.2 to 10.0.7.
Release notes
Sourced from Microsoft.Extensions.Hosting's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.ML.OnnxRuntime from 1.23.2 to 1.25.1.
Release notes
Sourced from Microsoft.ML.OnnxRuntime's releases.
1.25.1
n.b. This changelog is LLM generated. Only the contributor listing has been verified.
ONNX Runtime Release 1.25.1
📢 Announcements & Breaking Changes
ONNX Op Updates
✨ New Features
📊 New ONNX Ops & Model Support
🌐 Web & JavaScript
WebGPU EP
🐛 Bug Fixes
Core Runtime Fixes
SetRawDataInTensorProtoin NVIDIA TensorRT RTX tests (#28065)🙏 Contributors
Thanks to our 7 contributors for this release:
@guschmue, @sanaa-hamel-microsoft, @apsonawane, @eserscor, @ishwar-raut1, @qjia7, @theHamsta
Full Changelog: microsoft/onnxruntime@v1.25.0...v1.25.1
1.25.0
📢 Announcements & Breaking Changes
Build & Platform
Execution Provider Changes
--use_armnnbuild flags and migrate to the MLAS/KleidiAI-backed CPU EP or QNN EP for Qualcomm hardware. (#27447)API Version
🔒 Security Fixes
onnx::TensorProtodata size before allocation (#27547)✨ New Features
🔌 Execution Provider Plugin API & CUDA Plugin EP
... (truncated)
1.24.4
This is a patch release for ONNX Runtime 1.24, containing bug fixes and execution provider updates.
Bug Fixes
nvidia-drmis not loaded but GPU PCI devices are still exposed via sysfs. (#27591)GetOutputIndex. (#27644)Execution Provider Updates
Build and Infrastructure
python_requiresfrom>=3.10to>=3.11to reflect dropped Python 3.10 support. (#27354)__builtin_ia32_tpausewith the compiler-portable_tpauseintrinsic to fix cross-compiler portability issues between GCC and LLVM. (#27607)Full Changelog: v1.24.3...v1.24.4
Contributors
@derdeljan-msft, @adrianlizarraga, @apwojcik, @baijumeswani, @edgchen1, @mocknen, @tianleiwu, @XXXXRT666
1.24.3
This is a patch release for ONNX Runtime 1.24, containing bug fixes, security improvements, performance enhancements, and execution provider updates.
Security Fixes
Bug Fixes
OrtEnv.DisableDllImportResolverto prevent fatal error on resolver conflict. (#27535)Performance Improvements
Execution Provider Updates
wasmBinaryis provided. (#27318)wasmBinarytogether with a blob URL for.mjs. (#27411)s_kernel_registry_vitisaiep.reset()indeinitialize_vitisai_ep(). (#27295)OrtEpDeviceinstances for plugin and provider bridge EPs. (#27522)Build and Infrastructure
-Warray-boundsbuild error in MLAS on clang 17+. (#27499)kMaxValueLengthto 8192. (#27521)... (truncated)
1.24.2
This is a patch release for ONNX Runtime 1.24, containing several bug fixes, security improvements, and execution provider updates.
Bug Fixes
SparseTensorProtoToDenseTensorPrototo improve robustness. (#27323)ArrayFeatureExtractor. (#27275)Execution Provider Updates
LazyReleasefor prepack allocator. (#27077)ConvTransposebias validation in both TypeScript and C++ implementations. (#27213)Build and Infrastructure
Microsoft.ML.OnnxRuntime.Foundrypackage for Windows ARM64 support and NuGet signing. (#27294)BaseTesterto support plugin EPs with both compiled nodes and registered kernels. (#27176)Full Changelog: v1.24.1...v1.24.2
Contributors
@tianleiwu, @hariharans29, @edgchen1, @xiaofeihan1, @adrianlizarraga, @angelser, @angelserMS, @ankitm3k, @baijumeswani, @bmehta001, @ericcraw, @eserscor, @fs-eire, @guschmue, @mc-nv, @qjia7, @qti-monumeen, @titaiwangms, @yuslepukhin
1.24.1
📢 Announcements & Breaking Changes
Platform Support Changes
API Version
✨ New Features
🤖 Execution Provider (EP) Plugin API
A major infrastructure enhancement enabling plugin-based EPs with dynamic loading:
OrtKernelInfoAPIs for kernel-based plugin EPs (#26803)🔧 Core APIs
OrtApi::CreateEnvWithOptions()andOrtEpApi::GetEnvConfigEntries()(#26971)KernelInfo(#26589)📊 Dependencies & Integration
🖥️ Execution Provider Updates
NVIDIA
Qualcomm QNN EP
Intel & AMD
... (truncated)
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.0.1 to 18.5.1.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.5.1
What's Changed
Full Changelog: microsoft/vstest@v18.5.0...v18.5.1
18.5.0
What's Changed
Full Changelog: microsoft/vstest@v18.4.0...v18.5.0
18.4.0
What's Changed
Add LoongArch64 support by @stdmnpkg in Add LoongArch64 support microsoft/vstest#15359
Refactor Condition evaluation by @Youssef1313 in Refactor Condition evaluation microsoft/vstest#15357
Adding info on extensions points part 1 by @nohwnd in Adding info on extensions points part 1 microsoft/vstest#15360
Add option to ask for uploading code QL before the standard window ends by @nohwnd in Add option to ask for uploading code QL before the standard window ends microsoft/vstest#15373
Update runtime versions by @nohwnd in Update runtime versions microsoft/vstest#15372
Fix .NET 10 regression for traits by @Youssef1313 in Fix .NET 10 regression for traits microsoft/vstest#15370
Update target frameworks to net10.0 and net11.0 by @dotnet-maestro[bot] in Update target frameworks to net10.0 and net11.0 microsoft/vstest#15349
Fix names in pipeline matrix so we don't have to align them by @nohwnd in Fix names in pipeline matrix so we don't have to align them microsoft/vstest#15365
Update SECURITY.md by @Youssef1313 in Update SECURITY.md microsoft/vstest#15342
New Contributors
Full Changelog: microsoft/vstest@v18.3.0...v18.4.0
18.3.0
What's Changed
Internal fixes and updates
New Contributors
Commits viewable in compare view.
Updated ModelContextProtocol from 0.8.0-preview.1 to 1.2.0.
Release notes
Sourced from ModelContextProtocol's releases.
1.2.0
This release improves stateless HTTP transport defaults and documentation with a breaking behavioral change that we are considering as a server reliability fix and therefore not bumping the major version with this release. Legacy SSE endpoints are now disabled by default with a new
HttpServerTransportOptions.EnableLegacySseproperty available to opt back into responding to the SSE endpoints; the property is marked as an[Obsolete]warning as we expect to remove this property in a future major version.A warning-level
[Obsolete]attribute is also applied to theRequestContext(McpServer, JsonRpcRequest)constructor, and theRequestContext(McpServer, JsonRpcRequest, TParams)overload should be used instead. This change contributes to fixes including DI scope lifetime in task-augmented tools, meta/progress combination failures, and outgoing message filter routing. We plan to remove the obsolete overload in a future major version.Breaking Changes
Refer to the C# SDK Versioning documentation for details on versioning and breaking change policies.
1. Disable legacy SSE by default #1468
MapMcp()no longer maps/sseand/messageendpoints by default. Servers whose clients connect via SSE will find those endpoints removed.Migrating from legacy SSE
If your clients connect to a
/sseendpoint (e.g.,https://my-server.example.com/sse), they were using the legacy SSE transport--if not running inStatelessmode. The/sseand/messageendpoints are now disabled by default (EnableLegacySseisfalseand marked[Obsolete]with diagnosticMCP9004). Upgrading the server SDK without updating clients will break SSE connections.Client-side migration. Change the client
Endpointfrom the/ssepath to the root MCP endpoint — the same URL your server passes toMapMcp(). For example:With the default
HttpTransportMode.AutoDetecttransport mode, the client automatically tries Streamable HTTP first. You can also setTransportMode = HttpTransportMode.StreamableHttpexplicitly if you know the server supports it.Server-side migration. If you previously relied on
/ssebeing mapped automatically, you now needEnableLegacySse = true(suppressing theMCP9004warning) to keep serving those endpoints. The recommended path is to migrate all clients to Streamable HTTP and then removeEnableLegacySse.Transition period. If some clients still need SSE while others have already migrated to Streamable HTTP, set
EnableLegacySse = truewithStateless = false. Both transports are served simultaneously byMapMcp()— Streamable HTTP on the root endpoint and SSE on/sseand/message. Once all clients have migrated, removeEnableLegacySseand optionally switch toStateless = true.SSE (legacy — opt-in only)
Legacy SSE endpoints are now disabled by default and must be explicitly enabled via
HttpServerTransportOptions.EnableLegacySse. This is the primary reason they are disabled — the SSE transport has no built-in HTTP-level backpressure.The legacy SSE transport separates the request and response channels: clients POST JSON-RPC messages to
/messageand receive responses through a long-lived GET SSE stream on/sse. The POST endpoint returns 202 Accepted immediately after queuing the message — it does not wait for the handler to complete. This means there is no HTTP-level backpressure on handler concurrency, because each POST frees its connection immediately regardless of how long the handler runs.Internally, handlers are dispatched with a fire-and-forget pattern. A client can send unlimited POST requests to
/messagewhile keeping the GET stream open, and each one spawns a concurrent handler with no built-in limit.The GET stream does provide session lifetime bounds: handler cancellation tokens are linked to the GET request's
HttpContext.RequestAborted, so when the client disconnects the SSE stream, all in-flight handlers are cancelled. This is similar to SignalR's connection-bound lifetime model — but unlike SignalR, there is no per-client concurrency limit likeMaximumParallelInvocationsPerClient. The GET stream provides cleanup on disconnect, not rate-limiting during the connection.2. Obsolete 2-arg RequestContext constructor #1462
The
RequestContext(McpServer, JsonRpcRequest)constructor is now[Obsolete]with diagnosticMCP9003, producing build warnings. TheParamsproperty is also changed fromTParams?toTParams.Migration: Use the new 3-arg constructor:
new RequestContext(server, request, parameters).What's Changed
... (truncated)
1.1.0
Highlights of v1.1.0 include client completion details for understanding when and why a client connection ended, auto-populated completion handlers from
AllowedValuesAttribute, and bug fixes for server-initiated ping handling, server capabilities initialization, and in-flight message handler cleanup.What's Changed
Documentation Updates
Repository Infrastructure Updates
EnablePackageValidationfor all src packages with1.0.0baseline #1330 by @jeffhandley (co-authored by @Copilot @stephentoub)Acknowledgements
Full Changelog: modelcontextprotocol/csharp-sdk@v1.0.0...v1.1.0
1.0.0
This is the first stable release of the ModelContextProtocol C# SDK. Thank you to all of the contributors who helped us achieve this milestone!
Breaking Changes
Refer to the C# SDK Versioning documentation for details on versioning and breaking change policies.
HttpServerTransportOptions.RunSessionHandleris now annotated with[Experimental("MCPEXP002")]RunSessionHandlerwill produce a compile-time warning (or error withTreatWarningsAsErrors); suppress with#pragma warning disable MCPEXP002ConfigureSessionOptionsas an alternative;RunSessionHandlermay be removed or change signatures in a future releaseWhat's Changed
RunSessionHandlerexperimental (MCPEXP002) #1383 by @halter73 (co-authored by @Copilot @jeffhandley)Documentation Updates
Repository Infrastructure Updates
Acknowledgements
Full Changelog: modelcontextprotocol/csharp-sdk@v1.0.0-rc.1...v1.0.0
1.0.0-rc.1
This release candidate completes a full API surface area audit ahead of the 1.0.0 stable release, with more changes to public APIs to ensure consistency and long-term maintainability. Protocol DTO types are updated to match the MCP specification, deprecated filter APIs are removed, and bug fixes improve transport reliability and JSON handling.
Breaking Changes
Refer to the C# SDK Versioning documentation for details on versioning and breaking change policies.
Address asymmetry in McpServerHandlers/McpClientHandlers and make all filter properties settable #1337
McpClientHandlersto match the already-sealedMcpServerHandlersMcpServerOptions.Handlers,McpServerOptions.Filters, and allIList<T>filter properties settable with null validationRemove server back-references from protocol DTO types #1345
Tool.McpServerTool,Prompt.McpServerPrompt,Resource.McpServerResource, andResourceTemplate.McpServerResourcepropertiesMcpServerPrimitiveCollection.TryGetPrimitive()for name-based lookups insteadMake Tool.Name required to match other protocol types #1351
requiredmodifier toTool.Name, matchingPrompt.Name,Resource.Name, and otherIBaseMetadataimplementationsNamein object initializersMake LoggingMessageNotificationParams.Data required per MCP spec #1353
LoggingMessageNotificationParams.DatafromJsonElement?torequired JsonElementper the MCP specificationFix CreateMessageRequestParams.Metadata type to JsonObject #1354
CreateMessageRequestParams.MetadatafromJsonElement?toJsonObject?to match all other_meta/Metaproperties in the SDKNormalize CallToolResult.StructuredContent to JsonElement? #1357
CallToolResult.StructuredContentfromJsonNode?toJsonElement?for consistency with the rest of the SDKJsonSerializer.SerializeToElement()to produce aJsonElementUnify service configuration for
ISseEventStreamStore,IMcpTaskStore, andISessionMigrationHandler#1362Add explicit [Experimental] protected constructors to McpClient and McpServer #1363
McpClientandMcpServernow require suppressingMCPEXP002to subclassRemove MCP9002 obsolete APIs and document obsolete diagnostics #1366
AddXxxFilterextension methods onIMcpServerBuilder(e.g.AddCallToolFilter,AddListToolsFilter) that were deprecated under diagnosticMCP9002WithRequestFilters()andWithMessageFilters()insteadFix McpClientPrompt/Resource types to use RequestOptions like McpClientTool does #1370
JsonSerializerOptionswithRequestOptionsparameter for consistency acrossMcpClientPrompt,McpClientResource, andMcpClientToolWhat's Changed
... (truncated)
0.9.0-preview.2
This release focuses on API surface consistency and correctness ahead of 1.0.0. Public collection properties are now typed as
IList<T>instead of concreteList<T>orT[], andRoot.Metais aligned with the rest of the protocol DTOs by usingJsonObject?. Other improvements include new experimental Extensions support for capabilities, missingResourceLinkBlockproperties, improved mimeType handling, and several documentation and test reliability fixes.We plan to release the stable 1.0.0 release early in the week of February 23, 2026.
Breaking Changes
Refer to the C# SDK Versioning documentation for details on versioning and breaking change policies.
Replace concrete collection types with interfaces in public API surface #1326
List<T>andT[]properties onProtectedResourceMetadata,ToolResultContentBlock,ListTasksResult, andDynamicClientRegistrationResponsechanged toIList<T>. Replace.Lengthwith.Countand cast toList<T>ifList<T>-specific members are needed.Fix
Root.Metato useJsonObjectinstead ofJsonElement#1341Root.Metachanged fromJsonElement?toJsonObject?. Replacemeta.Value.GetProperty("key").GetString()with(string?)meta["key"].Make
UrlElicitationRequiredErrorData.Elicitationsconsistent with other Protocol DTOs #1335Elicitationschanged fromIReadOnlyList<ElicitRequestParams>withinittoIList<ElicitRequestParams>withset. Code usingList<T>is unaffected since it implements both interfaces.What's Changed
options ??= new()in McpServerImpl constructor #1322 by @stephentoub (co-authored by @Copilot)_connectCtsfield fromMcpClientImpl#1323 by @stephentoub (co-authored by @Copilot)Documentation Updates
Test Improvements
Repository Infrastructure Updates
Acknowledgements
... (truncated)
0.9.0-preview.1
The 0.9.0-preview.1 release includes multiple breaking changes focused on quality, extensibility, usability, and API consistency as we continue refining the SDK in preparation for a stable 1.0.0 release.
We plan to release the stable 1.0.0 release early in the week of February 23, 2026.
Breaking Changes
Refer to the C# SDK Versioning documentation for details on versioning and breaking change policies.
Use ReadOnlyMemory<byte> for binary data to eliminate UTF-16 transcoding #1070
ImageContentBlock.Data,AudioContentBlock.Data, andBlobResourceContents.Blobchanged fromstringtoReadOnlyMemory<byte>;FromImage/FromAudiorenamed toFromBytes;BlobResourceContents.Datarenamed toDecodedDataDecodedDatafor decoded bytes andFromBytes(...)factory methodsSplit configuration of request and message filters #1308
Add*Filterextension methods onIMcpServerBuilderreplaced byWithMessageFiltersandWithRequestFilterscallbacks with grouped builder instancesDon't treat McpServerHandlers as an independent options type #1313
McpServerHandlersno longer resolved viaIOptions<McpServerHandlers>; handlers set directly onMcpServerOptions.HandlersMcpServerOptionsdirectlyAdd
ISessionMigrationHandler#1270initializerequestModelContextProtocol.AspNetCore.AllowNewSessionForNonInitializeRequests=truerestores previous behaviorChange ProtectedResourceMetadata URI properties to strings #1264
Uri?/List<Uri>tostring?/List<string>to avoid unwanted URI normalizationUriobjectsHide experimental types from external source generators using internal property pattern #1301
[JsonIgnore]+ internal delegate pattern; external source generators no longer reference experimental typesValidate MCP-Protocol-Version header in Streamable HTTP handler #1277
Update McpErrorCode and fix error code usage to align with MCP spec #1291
MethodNotFoundtoInvalidParamsWhat's Changed
... (truncated)
Commits viewable in compare view.
Updated NUnit from 4.4.0 to 4.5.1.
Release notes
Sourced from NUnit's releases.
4.5.1
See release notes for details.
4.5.0
See release notes for details.
Commits viewable in compare view.
Updated NUnit.Analyzers from 4.11.2 to 4.12.0.
Release notes
Sourced from NUnit.Analyzers's releases.
4.12.0
NUnit Analyzers 4.12 - March 3, 2026
This release of the NUnit Analyzers improves
NUnit1029to account forTestCaseSourcesupport for params and optional arguments. It also introduces a new analyzer for incorrect
usage of
Is.Not.Null.Or.Empty, fixes regressions inNUnit2005andNUnit2055, and updatesNUnit package dependencies.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Is.Not.Null.Or.EmptyusedBugs
NUnit2055can generate invalid code for classic assertsNUnit2005tries to useIs.Emptyconstraint on incompatible types.Tooling, Process, and Documentation
Commits viewable in compare view.
Updated NUnit3TestAdapter from 6.1.0 to 6.2.0.
Release notes
Sourced from NUnit3TestAdapter's releases.
6.2.0
See release notes
Commits viewable in compare view.
Updated YamlDotNet from 16.3.0 to 17.1.0.
Release notes
Sourced from YamlDotNet's releases.
17.1.0
What's Changed
There was a potential breaking change for large yaml files in the MergingParser. You may need to specify the optional parameter for maximum events to be processed. It default to 100k events which is a very large yaml file.
Full Changelog: aaubry/YamlDotNet@v17.0.0...v17.1.0
17.0.0
What's Changed
_Description has been...
Description has been truncated