Repository navigation
Bump the all-dependencies group with 4 updates - #1465
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps AngleSharp from 1.8.6 to 1.9.1 Bumps DnsClientX from 2.1.2 to 2.2.0 Bumps Mailozaurr from 3.0.5 to 3.0.6 Bumps ModelContextProtocol from 1.4.1 to 2.3.0 --- updated-dependencies: - dependency-name: AngleSharp dependency-version: 1.9.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: all-dependencies - dependency-name: DnsClientX dependency-version: 2.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: all-dependencies - dependency-name: Mailozaurr dependency-version: 3.0.6 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: all-dependencies - dependency-name: ModelContextProtocol dependency-version: 2.3.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
|
Superseded by #1467, which includes the same AngleSharp, Mailozaurr and DnsClientX updates and ModelContextProtocol 2.3.1. The replacement passed Windows, Linux, macOS and dependency submission and is merged. |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Updated AngleSharp from 1.8.6 to 1.9.1.
Release notes
Sourced from AngleSharp's releases.
1.9.1
Released on Sunday, November 1 2026.
What's Changed
AppendChild,InsertBefore, ...) into a deep tree (#1401) @michaelthyregodclassList.toggle(token, false)adding an absent token instead of removing it: the DOM'stoggleis nowDomTokenListExtensions.ToggleToken:nth-child(… of …)selectors (#1403) @michaelthyregodFull Changelog: AngleSharp/AngleSharp@v1.9.0...v1.9.1
1.9.0
Released on Friday, October 30 2026.
What's Changed
TextContent,:contains(),GetElementById,GetElementsByName,GetElementsByClassName,GetElementsByTagNameandNormalize, which also continue with an explicit stack below 128 levels instead of recursing (#1389) @michaelthyregodIHtmlParser.ParseFragmentand of inserting many nodes at once (Append,Prepend, ...): finding a template's host no longer scans the whole document, and removing a node's last child no longer scans its siblingsinnerHTML) takes linear time; each node with children also allocates one object lesstable, a text run split by ignored end tags (x</q>x</q>...), and repeatedhtml/bodystart tags piling up attributes; attribute name lookups on elements with many attributes no longer scan them:has(): relative arguments only walk what they can reach (:has(> a)the descendants,:has(+ a)/:has(~ a)the following siblings) instead of the parent's whole subtree, the walk no longer allocates, and a:has()is tested after the rest of its compound and its ancestor chain, so rules such as.tree :has(.skeleton):hoveronly walk subtrees of hovered elements inside.treesetIntervalwith a delay of 0 never yielding: every round completed synchronously and queued tasks until memory ran out; a negative delay ofsetTimeoutorsetIntervalthrew instead of counting as 0 (nested intervals now wait at least 4ms, as in browsers)ParseFragment,innerHTML) to break out ofsvg/mathon HTML start tags such asp,bordiv, which previously stayed foreign elementsCreateElement<TElement>()depending on reflection that trimming can break;IElement,IHtmlElementandISvgElementnow throw instead of returning an arbitrary element @michaelthyregodIHtmlParser.ParseFragmentto keep an SVG or MathML context element in its namespace (and anannotation-xmlcontext'sencoding), instead of parsing as if the context were an HTML element of the same name, and to find aformancestor of the context, so a nested<form>start tag is ignored as withinnerHTMLtemplateinto its own contents not throwing aHierarchyRequestErrorAwaitEventAsyncremoving its listener off-thread while a dispatch was still running (#1397) @michaelthyregodIHtmlSelectElement.SelectedIndexgaining a setter; setOptions.SelectedIndexto change the selection (#1395) @SimonCroppAwaitEventAsyncoverload taking aCancellationToken@michaelthyregodIsAotCompatible) for the .NET 8 and .NET 10 targets (#1398) @michaelthyregodSubmitAsync,Attr,VirtualResponse.HeadersandToDictionary, which calls with an anonymous object bind to when recompiled; theObjectoverloads are now obsolete @michaelthyregodNew Contributors
Full Changelog: AngleSharp/AngleSharp@v1.8.6...v1.9.0
Commits viewable in compare view.
Updated DnsClientX from 2.1.2 to 2.2.0.
Release notes
Sourced from DnsClientX's releases.
2.2.0
2.2.0 - 2026-11-02
The CLI archives cover Windows, Linux and macOS on x64 and ARM64. They are framework-dependent: choose the .NET 8 or .NET 10 archive matching your installed runtime. Windows CLI executables are signed.
Publish the core NuGet package, PowerShell module and CLI archives without optional provider dependencies.
DnsClientX.Odoh,DnsClientX.DnsCryptandDnsClientX.DnsSec.EdDsaare not published on NuGet and are excluded from this release; their examples require source-built providers.Include the DNS correctness, configuration, DNSSEC, cache and cross-platform workflow fixes from #581, authenticated DNS administration and discovery workflows from #582, and stable resolver-candidate identity and reporting from #583.
Add a deterministic provider-by-transport JSON catalog at
Assets/Data/provider-profiles.json, generated with the README from the library's supported formats and default configurations. Packaged-module validation checks both outputs against the library.Refresh dependencies and improve regression coverage across the supported .NET and PowerShell targets.
Normalize recognized JSON EDE comments into structured extended DNS errors without replacing provider comments or explicit error arrays.
Select published provider transports without changing existing preset defaults, with shared provider definitions for configuration, resolver expansion and generated documentation.
Configure DNSCrypt and ODoH providers from role-specific DNS stamps, inspect privacy stamps from CLI/PowerShell, and load trusted optional providers explicitly for queries without adding crypto dependencies to the core or CLI.
Add New-DnsPrivacyTransport for caller-owned PowerShell setup and CLI privacy query options using the shared response and explanation workflow.
Preserve completed TCP/DoT replies when a peer closes while the request write finishes, avoiding a false failure and duplicate retry.
Add
data_normalizedto record JSON while preserving the existing rawdatafield.Show provider diagnostics in regular CLI text output and include DNS status in PowerShell warnings through shared display-safe formatting.
Give cooperative PowerShell query cleanup up to one second to finish when the pipeline is stopped, using the canonical async cmdlet implementation.
Add CleanBrowsing Security, Adult, and Family DoH presets, and Control D Unfiltered, Malware, Ads & Tracking, and Family DoH presets.
Add Comodo Secure DNS and DNS.WATCH plain-DNS presets, including DNS.WATCH's IPv6 resolvers.
Refresh AdGuard presets to the current
adguard-dns.comhostnames and share their endpoint definitions with multi-resolver queries.Document personal NextDNS profile URLs and distinguish generic resolution, filtering policy, and encrypted transports.
Commits viewable in compare view.
Updated Mailozaurr from 3.0.5 to 3.0.6.
Release notes
Sourced from Mailozaurr's releases.
3.0.6
What's Changed
Full Changelog: EvotecIT/Mailozaurr@Mailozaurr-v3.0.5...Mailozaurr-v3.0.6
Commits viewable in compare view.
Updated ModelContextProtocol from 1.4.1 to 2.3.0.
Release notes
Sourced from ModelContextProtocol's releases.
2.3.0
This release improves HTTP discovery, OAuth, protocol interoperability, and shutdown reliability, preserves registration order for server primitives, and exposes a
TimeProviderfor deterministic client timeout tests. It also corrects optional server-identity handling; applications readingMcpClient.ServerInfoshould adopt nullable handling.Breaking Changes
Refer to the C# SDK Versioning documentation for details on versioning and breaking change policies.
McpClient.ServerInfois nullable — #1903ImplementationtoImplementation?. Existing non-nullable assignments or dereferences can produce nullable warnings and fail warnings-as-errors builds.2026-07-28connections,ServerInfoisnullwhen the server omits optional identity metadata fromserver/discover. Legacyinitializestill requiresserverInfo. Reading the property before connecting still throwsInvalidOperationException.client.ServerInfo?.Name ?? "Unknown server". Self-reported identity must not be used for security decisions.What's Changed
ServerInfonullable #1903 by @Coding-ProfessionalDiscoverProbeTimeout, exposeMcpClientOptions.TimeProviderfor deterministic timeout tests, and default SSE to legacy initialization #1719 by @halter73 (co-authored by @Copilot)InitializationTimeoutand caller cancellation; it is excluded only from the short discovery-probe budget.HttpTransportMode.SseandProtocolVersion = "2026-07-28"; pinning the version withAutoDetectis not equivalent.RequestOptionsserialization #1832 by @dfedoryshchevDocumentation Updates
Test Improvements
Repository Infrastructure Updates
McpServerFactoryreferences in Copilot instructions #1892 by @Zir0-93Acknowledgements
... (truncated)
2.2.0
This release adds hybrid stateful/stateless HTTP serving so clients using the 2025-11-25 and 2026-07-28 protocol revisions can share an endpoint, and fixes a malformed header-decoding edge case.
What's Changed
Test Improvements
Repository Infrastructure Updates
Acknowledgements
Full Changelog: modelcontextprotocol/csharp-sdk@v2.1.0...v2.2.0
2.1.0
This release adds an opt-in
subscriptions/listenhandler for custom server-side notification streams, improves HTTP transport fallback reliability, and expands guidance and samples for telemetry and binary resources.What's Changed
Documentation Updates
Test Improvements
Repository Infrastructure Updates
> [!NOTE]alert example #1771 by @PranavSenthilnathan (co-authored by @Copilot)Acknowledgements
Full Changelog: modelcontextprotocol/csharp-sdk@v2.0.0...v2.1.0
2.0.0
Version 2.0.0 brings the C# SDK into stable alignment with the MCP 2026-07-28 specification.
This major release introduces discovery-first negotiation, multi-round-trip requests, stateless-by-default HTTP, caching hints, standardized headers, stronger OAuth and token-cache safety, and dedicated MCP Apps and Tasks extension packages, with down-level interoperability for peers negotiating 2025-11-25 and earlier. Review the migration guidance below.
Breaking Changes
Refer to the C# SDK Versioning documentation for details on versioning and breaking-change policies.
HttpServerTransportOptions.Statelessnow defaults totrue. Stateless servers do not create transport sessions, expose the standalone SSEGET/DELETEendpoints, or support unsolicited server-to-client requests.Stateless = falsewhen an existing server requires legacy stateful behavior. Stateful-only options now produceMCP9006warnings and apply only to down-level initialize-handshake connections.server/discoverfirst and automatically fall back to the legacyinitializehandshake for down-level servers.MCP9005warnings because these features are deprecated by the 2026-07-28 specification.MCP9005temporarily if continued use is required while planning migration.ModelContextProtocol.Extensions.Tasks#1693ModelContextProtocol.Extensions.Tasks, import its namespace, register Tasks withWithTasks(...), and replace CoreRequestMethods.Tasks*constants withTasksProtocolmembers.AuthorizationRedirectDelegateandClientOAuthOptions.AuthorizationRedirectDelegatenow produceMCP9007warnings. Migrate toClientOAuthOptions.AuthorizationCallbackHandlerso callbacks can return the authorization code, state, and issuer.UseStructuredContent = trueand a non-object return type now emit the raw value and matching schema, such asstructuredContent: 72, instead of wrapping it as{ "result": 72 }.resultproperty.Tool.inputSchemaduring deserialization #1600Toolpayload withoutinputSchemanow throwsJsonExceptioninstead of silently defaulting the schema.inputSchema; an empty{}is sufficient.S256incode_challenge_methods_supported.application_typeduring dynamic client registration #1613application_type.DynamicClientRegistrationOptions.ApplicationTypeexplicitly when the inferred value is not appropriate.HttpRequestException,TimeoutException, or genuine I/O exception instead of always wrapping failures inIOException.IOException("Failed to connect transport.")wrapper. In AutoDetect mode, inspect the outerHttpRequestExceptionand its inner SSE failure.insufficient_scopechallenge that introduces no new scopes now throwsMcpExceptioninstead of retrying indefinitely.What's Changed
InheritEnvironmentVariablestoStdioClientTransportOptions#1563 by @halter73offline_accessto authorization scope when advertised (SEP-2207) #1479 by @stephentoub (co-authored by @Copilot)McpErrorCode.ResourceNotFoundper SEP-2164 #1558 by @jayaraman-venkatesanMcpClienttool cache #1590 by @tarekghScopeSelectorDelegateto OAuth options #1596 by @halllo... (truncated)
2.0.0-rc.2
This second 2.0 release candidate advances the SDK’s
2026-07-28protocol support, expands Tasks extension conformance tests, strengthens OAuth and transport behavior, and expands 2.0 guidance ahead of general availability.Thank you to the community for using the preview and release-candidate builds and for sharing feedback and issue reports that shape this release!
Breaking Changes
Refer to the C# SDK Versioning documentation for details on versioning and breaking-change policies.
DiscoverResult.ServerInfois removed; read and deserializeMeta[MetaKeys.ServerInfo]instead.2026-07-28, replace legacy initialization, ping, logging, and resource-subscription methods withserver/discover,_metalog level, andsubscriptions/listen.statethroughAuthorizationResult.State, and should returnCode,State, andIss.IOExceptionwrapper.What's Changed
Documentation Updates
Test Improvements
_meta.uiserialization round-trip tests #1698 by @yayayouyouRepository Infrastructure Updates
... (truncated)
2.0.0-rc.1
2.0.0-rc.1 advances the v2 SDK toward general availability with stronger OAuth conformance, improved dynamic client registration, and expanded Tasks validation.
We remain on-track to release 2.0.0 stable on or before 2026-07-28.
We want to give a big thanks to @KubaZ2 for reporting the critical, ship-stopping Tasks/HTTP defect in #1720, fixed by #1722!
Breaking Changes
Refer to the C# SDK Versioning documentation for details on versioning and breaking change policies.
Remove the preview task-scope helper #1722
McpTasksServerExtensions.CreateMcpTaskScope(...)was removed from the stable surface. This affects only applications built against the v2 preview API; no stable 2.0 release has shipped.Harden OAuth issuer validation #1605
AuthorizationRedirectDelegatenow producesMCP9007, which breaks warning-as-error builds; the manual authorization flow now requires the complete redirect URL.AuthorizationCallbackHandlerand returnAuthorizationResult.Require advertised PKCE S256 support #1700
code_challenge_methods_supported: ["S256"]now cause authentication to fail instead of receiving an inferred default.Send Dynamic Client Registration application types #1613
ApplicationTypenow sends an inferredapplication_typeinstead of omitting it.DynamicClientRegistrationOptions.ApplicationTypeexplicitly when the authorization server requires another value.What's Changed
application_typein Dynamic Client Registration requests #1613 by @jayaraman-venkatesan (co-authored by @Copilot)ClientOAuthProvider#1605 by @mikekistler (co-authored by @halter73 @Copilot)Documentation Updates
release/1.x(v1.4.1) andmain(v2 preview) content #1727 by @jeffhandley (co-authored by @Copilot)Test Improvements
... (truncated)
2.0.0-preview.3
This preview reorganizes the Tasks feature into its own
ModelContextProtocol.Extensions.Taskspackage, keepingModelContextProtocol.Corefocused on the base protocol while a new generic request-handler and alternate-result surface lets the Tasks package layer on top. It also delivers correctness fixes to the draft2026-07-28protocol -- per-request client capabilities, negotiation boundaries, and theresultTypediscriminator -- plus Streamable HTTP client improvements (an empty-JSON-response fix and a new standalone GET-stream opt-out) and conformance-test consolidation.Breaking Changes
Refer to the C# SDK Versioning documentation for details on versioning and breaking change policies.
ModelContextProtocol.Extensions.Taskspackage #1693McpTaskStatus,IMcpTaskStore/InMemoryMcpTaskStore, thetasks/*request methods, and the clientGetTaskAsync/UpdateTaskAsync/CancelTaskAsync/CallToolRawAsyncmethods -- is removed fromModelContextProtocol.Coreand relocated to the newModelContextProtocol.Extensions.Taskspackage under theModelContextProtocol.Extensions.Tasksnamespace.ResultOrAlternate<T>(replacingResultOrCreatedTask<T>) plus generic extension points --McpServerRequestHandler,McpServerOptions.RequestHandlers,McpServerHandlers.CallToolWithAlternateHandler,McpRequestFilters.CallToolWithAlternateFilters, andMcpServer.InterceptOutgoingRequests-- that the Tasks package builds on.PackageReferencetoModelContextProtocol.Extensions.Tasks; changeusing ModelContextProtocol.Protocol;tousing ModelContextProtocol.Extensions.Tasks;for task types; the task client/server APIs are now extension methods (McpTasksClientExtensions/McpTasksServerExtensions), and the task store is registered via the new builder extensions instead ofMcpServerOptions.TaskStore.Experimental APIs
To support extracting Tasks (#1693),
ModelContextProtocol.Coregained a generic server-extension surface --ResultOrAlternate<T>,McpServerRequestHandler,McpServerOptions.RequestHandlers,McpServerHandlers.CallToolWithAlternateHandler,McpRequestFilters.CallToolWithAlternateFilters, andMcpServer.InterceptOutgoingRequests-- that lets extension packages such asModelContextProtocol.Extensions.Taskslayer behavior onto the server pipeline. These APIs are annotated[Experimental]under diagnostic IDMCPEXP002.This surface is still being designed: #1704 tracks composing these seams with the normal filter and subscription pipeline (typed custom RPCs, filter composition, and extension-defined subscriptions). Expect these low-level extensibility APIs to change and potentially remain
[Experimental]through the 2.0.0 stable release.What's Changed
ModelContextProtocol.Extensions.Tasksextension package #1693 by @jeffhandley (co-authored by @Copilot)Test Improvements
Acknowledgements
Full Changelog: modelcontextprotocol/csharp-sdk@v2.0.0-preview.2...v2.0.0-preview.3
2.0.0-preview.2
This second preview of the 2.0.0 series advances the SDK's alignment with the upcoming
2026-07-28MCP protocol revision: it adds client-side conformance diagnostics for the SEP-2549 caching hints, makes Streamable HTTP error responses echo the request id per the base protocol and SEP-2243, and fully stabilizes now-stable protocol properties so consumer-defined source generators serialize them correctly. Separately -- and unrelated to the protocol revision -- it introducesDeferChangedEvents()onMcpServerPrimitiveCollection<T>for batchinglist_changednotifications when registering primitives in bulk. There are no breaking changes relative tov2.0.0-preview.1.What's Changed
Documentation Updates
Acknowledgements
Full Changelog: modelcontextprotocol/csharp-sdk@v2.0.0-preview.1...v2.0.0-preview.2
2.0.0-preview.1
This is the first preview of the C# MCP SDK 2.0.0, designed for alignment with the 2026-07-28 MCP specification release. The SDK implements the
2026-07-28protocol version which fundamentally changes how clients and servers interact -- removing theinitializehandshake (SEP-2575), eliminating server-side session state (SEP-2567), introducing Multi Round-Trip Requests (SEP-2322), and deprecating legacy capabilities in favor of the new extensions framework (SEP-2133).The 2.0.0 SDK is fully backward-compatible with servers and clients using the previous
2024-11-05protocol version. Clients automatically negotiate down to the legacyinitializehandshake when connecting to older servers, and servers continue to acceptinitializerequests from older clients. API breaking changes in 2.0.0 are limited to two categories: (1) APIs for capabilities deprecated by the new specification (Roots, Sampling, and Logging), which are now marked[Obsolete]with guidance toward their replacements, and (2) experimental APIs whose contracts changed as the specifications were finalized. Stable, non-deprecated APIs from 1.x continue to work without modification.Protocol Version Negotiation and Handshake Behavior
The 2.0.0 SDK introduces a fundamentally new connection lifecycle:
Default behavior (no configuration needed):
server/discoverrequest withMCP-Protocol-Version: 2026-07-282026-07-28protocol version, it responds with capabilities -- no handshake, no sessionMcpClientOptions.DiscoverProbeTimeout), the client automatically falls back to the legacyinitializehandshake with2025-11-25-32022UnsupportedProtocolVersion,-32021MissingRequiredClientCapability,-32020HeaderMismatch) are never treated as legacy indicators and are surfaced as errorsOpting out of the
2026-07-28protocol version:McpClientOptions.ProtocolVersion = "2025-11-25"to force the legacyinitializehandshake and disable the automatic fallback (a non-nullProtocolVersionnow acts as both the requested version and the minimum the client accepts)Per-request metadata (
2026-07-28protocol version):_metawithio.modelcontextprotocol/protocolVersion,io.modelcontextprotocol/clientInfo, andio.modelcontextprotocol/clientCapabilities2026-07-28 Spec Alignment: SEP Implementation Status
The 2026-07-28 specification release includes 22 SEPs. The table below summarizes C# SDK status. Remaining work is tracked in the 2026-07-28 Spec Compliance milestone.
1.4.2
This patch release includes security fixes for OAuth authentication and authenticated HTTP sessions.
What's Changed
Deployments using metadata-free 2025-03-26 OAuth discovery may explicitly enable the legacy endpoint fallback only after independently verifying PKCE enforcement; otherwise, update metadata to advertise S256. The process-wide opt-in is
ModelContextProtocol.Authentication.AllowLegacyOAuthMetadataFallback; it does not bypass validation of discovered metadata.Documentation Updates
Repository Infrastructure Updates
Acknowledgements
Full Changelog: modelcontextprotocol/csharp-sdk@v1.4.1...v1.4.2
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions