Skip to content

Bump the minor-and-patch group with 23 updates - #88

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/minor-and-patch-180859711d
Open

Bump the minor-and-patch group with 23 updates#88
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/minor-and-patch-180859711d

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 21, 2026

Copy link
Copy Markdown
Contributor

Updated Aspire.Hosting.AppHost from 13.5.4 to 13.6.2.

Release notes

Sourced from Aspire.Hosting.AppHost's releases.

13.6.2

Full commit: af07e33f8d1ef733645138b3f8e36067d073148d

What's Changed

Full Changelog: microsoft/aspire@v13.6.1...v13.6.2

13.6.1

What's New in Aspire 13.6.1

Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows.

🐛 Fixes

  • 📊 Dashboard CPU usage could increase during long-running metric ingestion — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes #​20725. (#​20747, backport of #​20736, @​JamesNK)

  • 📈 The Metrics tree could not be scrolled — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes #​20728. (#​20762, backport of #​20758, @​heyysiri)

  • 🧭 Dashboard navigation could fail after a browser disconnect — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. (#​20545, backport of #​20527, @​JamesNK)

  • 🖥️ Container exec watches could terminate shortly after AppHost startup — A stalled DCP watch connection could produce a critical Watch task over Kubernetes ContainerExec resources terminated unexpectedly error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. (#​20664, backport of #​20466, @​radical)

  • 🪟 Session-scoped containers could remain running after stopping a .NET AppHost on Windows — AppHosts launched through dotnet run or dotnet watch now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and aspire stop flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes #​20495. (#​20514, backport of #​20494, @​danegsta)

Full Changelog: v13.6.0...v13.6.1

Full commit: 3751e615ad660621f2a7aa4c390ef48e08a0eed8

13.6.0

Aspire 13.6.0

Aspire 13.6 brings persistent application history, a refreshed and more interactive dashboard, first-party Java and Rust hosting, and new Azure deployment options. Coordinated .NET builds, portable volume paths, sharper CLI workflows, and more capable editor tooling make it easier to build, debug, and deploy applications across languages.

Highlights

  • 🗃️ Persistent, refreshed dashboard — SQLite-backed telemetry and resource snapshots let you revisit up to ten application runs, with read-only access to completed runs and default retention limits of 100,000 console log messages, structured logs, and traces each. The dashboard now ships as Native AOT and adopts Fluent UI v5 with a collapsible navigation rail.
  • 🖥️ AppHost-owned terminals and database REPLs — Experimental terminal APIs let AppHosts create interactive sessions in a dashboard dock, dialog, or separate window. Opt-in WithRepl() commands open bundled clients for PostgreSQL, MySQL, MongoDB, SQL Server, Redis, and Valkey, while aspire terminal ps and aspire terminal tape play support discovery and repeatable terminal interactions.
  • 🌐 First-party Java and Rust hosting — New Aspire.Hosting.Java and Aspire.Hosting.Rust packages bring Maven, Gradle, Spring Boot, Quarkus, and Cargo applications into the app model, with generated container builds and VS Code debugging. These integrations build on work that originated in the Aspire Community Toolkit.
  • 🛠️ More flexible AppHosts — The prerelease Aspire.Hosting.Dotnet integration coordinates compatible projects into shared restore and build groups and supports .NET SDK container publishing. Portable volume-path environment variables work across local execution and deployment, while TypeScript AppHosts gain standard appsettings.json configuration and Deno runtime support.
  • ⌨️ Sharper CLI workflows — Select launch profiles with aspire run and aspire start, update repository-local CLI manifests with aspire update, create file-based C# AppHosts with aspire init --language csharp --file-based, and export TypeScript API data with aspire sdk export. Terminal commands no longer need a feature flag, Linux certificate trust includes Firefox NSS databases, and aspire stop --force --volumes adds explicit cleanup of Aspire-owned volumes.
  • 💻 More capable VS Code tooling — Coding agents can start and stop AppHosts through the extension, and the Aspire pane exposes deploy, publish, and pipeline actions. Multi-root discovery, worktree-scoped lifecycle operations, preserved launch arguments, clearer debug logs, and missing-debugger guidance make complex workspaces more predictable.
  • ☁️ New Azure options in preview — Azure Connector Namespace models external-service connections and managed MCP server configurations. Azure Container Apps Sandboxes adds isolated sandbox deployments with configurable resource tiers and lifecycle policies, while Azure Container Apps Express offers a simplified environment option for rapid provisioning.
  • ☸️ More expressive, reliable deployments — Experimental Azure Provisioning SDK proxies let polyglot AppHosts customize infrastructure. Deployment state is isolated under ASPIRE_HOME, Kubernetes preserves inherited hostnames and embedded parameter values, and AKS gains persistent-volume provisioning and more reliable cleanup.
  • 🔌 Expanded integrations — Experimental Deno hosting and MongoDB replica sets join Foundry Toolboxes, remote Foundry Local endpoints, Blazor WebAssembly debugging, and configurable Dev Tunnel expiration. Azure Cosmos DB and AI Inference client integrations gain health checks, and the vNext Cosmos DB emulator sends its own telemetry to the dashboard.

⚠️ Breaking changes

Notable changes include automatic TLS for local MongoDB servers when a certificate is available, the Linux-based vNext Cosmos DB emulator becoming the default, new Azure Front Door origin names that can require cleanup of existing origins, portable connection-string environment-variable aliases on stricter deployment targets, and experimental terminal types moving from Aspire.Hosting.Terminals to Aspire.Hosting.ApplicationModel.

See the full list and migration guidance in the Aspire 13.6 breaking changes.

📖 Learn more

For complete details, examples, migration guidance, and everything new in this release, read What's new in Aspire 13.6.

Thank you to all the community contributors who helped make Aspire 13.6 possible! 💜

Full Changelog: v13.5.4...v13.6.0

Full commit: 56f3e9c0d216c0c7069dabb49dd0464e4827744f

Commits viewable in compare view.

Updated Aspire.Hosting.Azure.CosmosDB from 13.5.4 to 13.6.2.

Release notes

Sourced from Aspire.Hosting.Azure.CosmosDB's releases.

13.6.2

Full commit: af07e33f8d1ef733645138b3f8e36067d073148d

What's Changed

Full Changelog: microsoft/aspire@v13.6.1...v13.6.2

13.6.1

What's New in Aspire 13.6.1

Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows.

🐛 Fixes

  • 📊 Dashboard CPU usage could increase during long-running metric ingestion — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes #​20725. (#​20747, backport of #​20736, @​JamesNK)

  • 📈 The Metrics tree could not be scrolled — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes #​20728. (#​20762, backport of #​20758, @​heyysiri)

  • 🧭 Dashboard navigation could fail after a browser disconnect — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. (#​20545, backport of #​20527, @​JamesNK)

  • 🖥️ Container exec watches could terminate shortly after AppHost startup — A stalled DCP watch connection could produce a critical Watch task over Kubernetes ContainerExec resources terminated unexpectedly error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. (#​20664, backport of #​20466, @​radical)

  • 🪟 Session-scoped containers could remain running after stopping a .NET AppHost on Windows — AppHosts launched through dotnet run or dotnet watch now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and aspire stop flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes #​20495. (#​20514, backport of #​20494, @​danegsta)

Full Changelog: v13.6.0...v13.6.1

Full commit: 3751e615ad660621f2a7aa4c390ef48e08a0eed8

13.6.0

Aspire 13.6.0

Aspire 13.6 brings persistent application history, a refreshed and more interactive dashboard, first-party Java and Rust hosting, and new Azure deployment options. Coordinated .NET builds, portable volume paths, sharper CLI workflows, and more capable editor tooling make it easier to build, debug, and deploy applications across languages.

Highlights

  • 🗃️ Persistent, refreshed dashboard — SQLite-backed telemetry and resource snapshots let you revisit up to ten application runs, with read-only access to completed runs and default retention limits of 100,000 console log messages, structured logs, and traces each. The dashboard now ships as Native AOT and adopts Fluent UI v5 with a collapsible navigation rail.
  • 🖥️ AppHost-owned terminals and database REPLs — Experimental terminal APIs let AppHosts create interactive sessions in a dashboard dock, dialog, or separate window. Opt-in WithRepl() commands open bundled clients for PostgreSQL, MySQL, MongoDB, SQL Server, Redis, and Valkey, while aspire terminal ps and aspire terminal tape play support discovery and repeatable terminal interactions.
  • 🌐 First-party Java and Rust hosting — New Aspire.Hosting.Java and Aspire.Hosting.Rust packages bring Maven, Gradle, Spring Boot, Quarkus, and Cargo applications into the app model, with generated container builds and VS Code debugging. These integrations build on work that originated in the Aspire Community Toolkit.
  • 🛠️ More flexible AppHosts — The prerelease Aspire.Hosting.Dotnet integration coordinates compatible projects into shared restore and build groups and supports .NET SDK container publishing. Portable volume-path environment variables work across local execution and deployment, while TypeScript AppHosts gain standard appsettings.json configuration and Deno runtime support.
  • ⌨️ Sharper CLI workflows — Select launch profiles with aspire run and aspire start, update repository-local CLI manifests with aspire update, create file-based C# AppHosts with aspire init --language csharp --file-based, and export TypeScript API data with aspire sdk export. Terminal commands no longer need a feature flag, Linux certificate trust includes Firefox NSS databases, and aspire stop --force --volumes adds explicit cleanup of Aspire-owned volumes.
  • 💻 More capable VS Code tooling — Coding agents can start and stop AppHosts through the extension, and the Aspire pane exposes deploy, publish, and pipeline actions. Multi-root discovery, worktree-scoped lifecycle operations, preserved launch arguments, clearer debug logs, and missing-debugger guidance make complex workspaces more predictable.
  • ☁️ New Azure options in preview — Azure Connector Namespace models external-service connections and managed MCP server configurations. Azure Container Apps Sandboxes adds isolated sandbox deployments with configurable resource tiers and lifecycle policies, while Azure Container Apps Express offers a simplified environment option for rapid provisioning.
  • ☸️ More expressive, reliable deployments — Experimental Azure Provisioning SDK proxies let polyglot AppHosts customize infrastructure. Deployment state is isolated under ASPIRE_HOME, Kubernetes preserves inherited hostnames and embedded parameter values, and AKS gains persistent-volume provisioning and more reliable cleanup.
  • 🔌 Expanded integrations — Experimental Deno hosting and MongoDB replica sets join Foundry Toolboxes, remote Foundry Local endpoints, Blazor WebAssembly debugging, and configurable Dev Tunnel expiration. Azure Cosmos DB and AI Inference client integrations gain health checks, and the vNext Cosmos DB emulator sends its own telemetry to the dashboard.

⚠️ Breaking changes

Notable changes include automatic TLS for local MongoDB servers when a certificate is available, the Linux-based vNext Cosmos DB emulator becoming the default, new Azure Front Door origin names that can require cleanup of existing origins, portable connection-string environment-variable aliases on stricter deployment targets, and experimental terminal types moving from Aspire.Hosting.Terminals to Aspire.Hosting.ApplicationModel.

See the full list and migration guidance in the Aspire 13.6 breaking changes.

📖 Learn more

For complete details, examples, migration guidance, and everything new in this release, read What's new in Aspire 13.6.

Thank you to all the community contributors who helped make Aspire 13.6 possible! 💜

Full Changelog: v13.5.4...v13.6.0

Full commit: 56f3e9c0d216c0c7069dabb49dd0464e4827744f

Commits viewable in compare view.

Updated bunit from 2.11.3 to 2.12.5.

Release notes

Sourced from bunit's releases.

2.12.5

Fixed

  • WrapperBase.WrappedElement could return null and throw NullReferenceException when an element was accessed concurrently with component re-renders. Reported by @​psu-prog in #​1937. Fixed by @​Nacl-HCl.
  • DisposeComponentsAsync() could dispose nothing when the renderer's dispatcher was busy, e.g. with a timer calling InvokeAsync. Reported by @​xfunc-tim-schneider in #​1939. Fixed by @​linkdotnet.
  • Markup generation and FindComponents could recurse until the test host crashed with a stack overflow when a render threw while instantiating a child component. Reported in #​1935. Fixed by @​linkdotnet.
  • Find() could keep returning DOM nodes from the previous render when a render, e.g. from a timer, happened while the nodes were parsed, causing UnknownEventHandlerIdException. Reported by @​xfunc-tim-schneider in #​1938. Fixed by @​linkdotnet.

Commits viewable in compare view.

Updated Microsoft.Azure.Cosmos from 3.63.1 to 3.63.2.

Release notes

Sourced from Microsoft.Azure.Cosmos's releases.

3.63.2

See changelog for details.
NuGet: https://www.nuget.org/packages/Microsoft.Azure.Cosmos/3.63.2

Commits viewable in compare view.

Updated Microsoft.Data.SqlClient from 7.1.0 to 7.1.1.

Release notes

Sourced from Microsoft.Data.SqlClient's releases.

7.1.1

This servicing release fixes decimal parameter validation, token expiry handling in connection pool V2, and connection opens that are in progress when a pool is cleared.

Package version alignment: The SqlClient family packages share the 7.1.1 version:

  • Microsoft.Data.SqlClient
  • Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider
  • Microsoft.Data.SqlClient.Extensions.Azure
  • Microsoft.Data.SqlClient.Extensions.Abstractions
  • Microsoft.Data.SqlClient.Internal.Logging

Microsoft.SqlServer.Server is versioned independently and is not part of this release. Applications should use matching 7.1.1 versions of the driver and its companion packages. The aligned assemblies retain AssemblyVersion 7.0.0.0; upgrading from 7.1.0 does not require new .NET Framework strong-name binding redirects.

Companion package release notes

Changes Since 7.1.0

Fixed

  • Fixed an ArgumentException when sending zero-valued decimal or SqlDecimal parameters whose precision equals their scale. Nonzero precision validation and support for large decimal values are unchanged. (#​4715, #​4721, #​4732)

  • Fixed connection pool V2 handing out pooled connections with expired or nearly expired access tokens. The pool now checks token expiry before reuse, matching the default pool's behavior while preserving transaction-affine reuse. This affects only applications that opt in to connection pool V2. (#​4734, #​4739)

  • Fixed connection opens failing when ClearPool or ClearAllPools races with an in-flight open. Requests already admitted to the cleared pool can finish, and connections returned to the retired pool are discarded rather than reused. (#​4714, #​4718, #​4740)

Target Platform Support

  • .NET Framework 4.6.2+ (Windows x86, Windows x64, Windows ARM64)
  • .NET 8.0+ (Windows x86, Windows x64, Windows ARM, Windows ARM64, Linux, macOS)

Dependencies

.NET 9.0

  • Microsoft.Bcl.Cryptography 9.0.18
  • Microsoft.Data.SqlClient.Extensions.Abstractions 7.1.1
  • Microsoft.Data.SqlClient.Internal.Logging 7.1.1
  • Microsoft.Data.SqlClient.SNI.runtime 7.1.0
  • Microsoft.Extensions.Caching.Memory 9.0.18
  • Microsoft.IdentityModel.JsonWebTokens 8.16.0
  • Microsoft.IdentityModel.Protocols.OpenIdConnect 8.16.0
  • Microsoft.SqlServer.Server 1.0.0
  • System.Configuration.ConfigurationManager 9.0.18
  • System.Security.Cryptography.Pkcs 9.0.18
  • System.Threading.RateLimiting 9.0.18

... (truncated)

Commits viewable in compare view.

Updated Microsoft.Data.Sqlite from 10.0.12 to 10.0.13.

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.AI.Abstractions from 10.10.1 to 10.11.0.

Release notes

Sourced from Microsoft.Extensions.AI.Abstractions's releases.

10.11.0

.NET Extensions 10.11.0

This release adds optional scope capture for buffered logs and updates experimental HTTP latency enrichment APIs. It also includes fixes for AI streaming and function invocation, evaluation reports, HybridCache invalidation, and logging.

Experimental API Changes

New Experimental APIs

  • Optional logging-scope capture for global and per-request log buffering through GlobalLogBufferingOptions.IncludeScopes and PerRequestLogBufferingOptions.IncludeScopes (EXTEXP0003) #​7813

Breaking Changes to Experimental APIs

  • Incoming HTTP latency log enrichment: AddHttpLatencyTelemetry is renamed to AddHttpServerLatencyTelemetry and moves from HttpLatencyTelemetryServiceCollectionExtensions to HttpLoggingServiceCollectionExtensions. It remains experimental under EXTEXP0013 in this release. #​7730

What's Changed

AI

  • Yield final image when streaming with HostedImageGenerationTool #​7774 by @​iamAdarshh
  • Make the default tool-rejection message state that the decision is final #​7784 by @​manjunathshiva
  • AI: Remove obsolete OpenAI JsonPatch workaround #​7815 by @​jozkee (co-authored by @​Copilot)
  • Ignore empty model IDs in streaming responses #​7816 by @​valkiara
  • Honor FunctionInvocationContext.Terminate when the function throws #​7801 by @​gjz22
  • Fix ChatResponseUpdate.Clone dropping ContinuationToken #​7699 by @​dfedoryshchev
  • Decode non-base64 data URIs in DataContent to the octets they encode #​7798 by @​Laurianti

AI Evaluation

  • [M.E.AI.Evaluation.Reporting] Fix context and metric interpretation visualization #​7738 by @​grafanaKibana
  • Fix tokenizer attaching punctuation to number tokens #​7766 by @​tahakocal
  • Order iteration results numerically #​7769 by @​tahakocal
  • Score GLEU against the best matching reference #​7768 by @​tahakocal

Telemetry and Observability

  • Optionally preserve logging scopes in buffered log records #​7813 by @​evgenyfedorov2 (co-authored by @​Copilot)
  • Fix OOM from unbounded enumeration of ExtendedLogger tag joiners #​7819 by @​evgenyfedorov2 (co-authored by @​Copilot)
  • Fix log buffering race by removing the rule selector cache #​7803 by @​evgenyfedorov2 (co-authored by @​Copilot)

ASP.NET Core Extensions

  • Rename AddHttpLatencyTelemetry to AddHttpServerLatencyTelemetry (API-approved shape) #​7730 by @​EasyL0ver (co-authored by @​Copilot)
  • Fix ArgumentNullException in per-request log buffering at the end of a request #​7811 by @​evgenyfedorov2 (co-authored by @​Copilot)

AI Project Templates

  • Align aichatweb local vector-store keys with Guid record keys #​7804 by @​jongalloway (co-authored by @​adamsitnik @​Copilot)

Caching

... (truncated)

Commits viewable in compare view.

Updated Microsoft.Extensions.Http from 10.0.12 to 10.0.13.

Release notes

Sourced from Microsoft.Extensions.Http's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 18.10.1 to 18.11.0.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

18.11.0

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v18.10.1...v18.11.0

Commits viewable in compare view.

Updated ModelContextProtocol from 2.2.0 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 TimeProvider for deterministic client timeout tests. It also corrects optional server-identity handling; applications reading McpClient.ServerInfo should adopt nullable handling.

Breaking Changes

Refer to the C# SDK Versioning documentation for details on versioning and breaking change policies.

  1. McpClient.ServerInfo is nullable — #​1903
    • Its return annotation changes from Implementation to Implementation?. Existing non-nullable assignments or dereferences can produce nullable warnings and fail warnings-as-errors builds.
    • On 2026-07-28 connections, ServerInfo is null when the server omits optional identity metadata from server/discover. Legacy initialize still requires serverInfo. Reading the property before connecting still throws InvalidOperationException.
    • Migrate with a null check or a fallback such as client.ServerInfo?.Name ?? "Unknown server". Self-reported identity must not be used for security decisions.
    • This corrective source-compatibility change is intentionally included in 2.3.0.

What's Changed

  • Correct protocol-version telemetry for stateless server spans #​1810 by @​luisangelrod
  • Preserve HTTP errors and correct discovery fallback handling #​1791 by @​PranavSenthilnathan (co-authored by @​Copilot)
  • Make modern Streamable HTTP status mapping deterministic #​1837 by @​jstar0
    • Modern responses wait for the first protocol message before sending headers; long-running silent handlers may need progress output or an appropriate HTTP timeout. Legacy eager-header behavior is preserved.
  • Accept opaque legacy metadata and correct request-scoped capabilities and discovery advertisement #​1852 by @​halter73 (co-authored by @​Copilot)
  • Avoid redundant SSE fallback after discovery is rejected with 400 or 404 #​1855 by @​scottt732
  • Close server stdin before waiting for graceful stdio process exit #​1838 by @​luisangelrod
  • Preserve insertion order when listing server tools, prompts, and resources #​1924 by @​PederHP (co-authored by Claude Opus 5.5)
  • Allow missing optional server identity in discovery and make ServerInfo nullable #​1903 by @​Coding-Professional
  • Include JSON parse details in Streamable HTTP 400 responses #​1844 by @​ump45nose
  • Exclude OAuth from DiscoverProbeTimeout, expose McpClientOptions.TimeProvider for deterministic timeout tests, and default SSE to legacy initialization #​1719 by @​halter73 (co-authored by @​Copilot)
    • OAuth remains subject to the overall InitializationTimeout and caller cancellation; it is excluded only from the short discovery-probe budget.
    • Modern discovery over SSE requires both explicit HttpTransportMode.Sse and ProtocolVersion = "2026-07-28"; pinning the version with AutoDetect is not equivalent.
  • Preserve numeric progress tokens in RequestOptions serialization #​1832 by @​dfedoryshchev
  • Dispose legacy SSE POST responses to release connections deterministically #​1841 by @​yalcinfu22 (co-authored by Claude Fable 5)

Documentation Updates

  • Document standing support for new MCP specification revisions #​1826 by @​halter73 (co-authored by @​Copilot)

Test Improvements

  • Stabilize discovery-capable test connections while retaining initialization deadlines #​1943 by @​tarekgh

Repository Infrastructure Updates

  • Add a source selector for manual documentation publishes #​1828 by @​jeffhandley (co-authored by @​Copilot)
  • Update SourceLink's private build dependency to resolve a vulnerable Git dependency #​1873 by @​halter73 (co-authored by @​Copilot)
  • Correct obsolete McpServerFactory references in Copilot instructions #​1892 by @​Zir0-93
  • Update Microsoft.Extensions.AI and AI.Abstractions to 10.11.0 and align shared System dependencies to 10.0.13 #​1940

Acknowledgements

  • @​scottt732 made their first contribution in #​1855
  • @​Zir0-93 made their first contribution in #​1892
  • @​Coding-Professional made their first contribution in #​1903
    ... (truncated)

Commits viewable in compare view.

Updated ModelContextProtocol.AspNetCore from 2.2.0 to 2.3.0.

Updated Quartz.Extensions.DependencyInjection from 3.22.3 to 3.22.7.

Release notes

Sourced from Quartz.Extensions.DependencyInjection's releases.

3.22.7

Fixes for the 3.x line, ported from 4.6. There is no public API change and no schema change.

Fixed

  • A trigger re-applied at startup keeps its previous fire time. Creating a scheduler re-applies the triggers the configuration registers through RescheduleJob, which replaced the stored trigger with one that had none, so PreviousFireTimeUtc was lost on every restart. It is now carried over when the replacement has none. (#​4127, from #​4122)
  • A recovered trigger keeps its job's execution group. A firing replayed after a node failure, a shutdown hand-back or startup recovery was stored ungrouped and ran beside a live firing of the same group, whatever the group's limit. (#​4085)
  • A manual firing carries the execution group its job's triggers share. TriggerJob and the dashboard's Trigger now carried none, so they ignored the group's limit. (#​4110)
  • Names in IConfiguration keep their case. A hierarchical section camel-cased every path segment on its way to the flat quartz.* keys, names the user chose included, and StdSchedulerFactory looks names up ordinally: Quartz:DataSource:MyDS beside Quartz:JobStore:DataSource = MyDS failed with no data source found. Data source, listener, execution-limit and context names now keep their case, and a plugin's name stays camel-cased, so the XML plugin's stored file-scan job keeps its key. (#​4108)
  • The dashboard's cron preview uses the trigger's time zone and calendar, and previews the expression being edited. (#​4118)

Warnings

  • A clustered scheduler warns when every node would share the instance id NON_CLUSTERED, which makes each node read the other's fired triggers as its own. Set quartz.scheduler.instanceId to AUTO, or a distinct id per node. 4.6 generates the id instead; 3.x keeps the default, because changing it would re-key an existing deployment's rows. (#​4106)
  • A generated job or trigger identity in a persistent store logs a warning: a generated key is new on every start, so a persistent store keeps another copy each time, and every copy of a trigger fires. Give it a stable key with WithIdentity. (#​4114)

What's Changed

Other changes

Full Changelog: quartznet/quartznet@v3.22.6...v3.22.7

3.22.6

One dependency fix for the 3.x line, from Microsoft's October 13 security advisories. There is no public API change and no schema change, and no other package changes.

Fixed

  • Quartz.Dashboard depends on Microsoft.AspNetCore.SignalR.Client 8.0.32. 3.22.5 depended on 8.0.8, whose Microsoft.AspNetCore.SignalR.Common GHSA-334f-vvp4-7g6p (CVE-2026-70159) covers, and 8.0.32 is the fixed version on the 8.x line. The fixed client raises Microsoft.Extensions.DependencyInjection, DependencyInjection.Abstractions, Logging and Logging.Abstractions within 8.0.x (to 8.0.1, 8.0.2, 8.0.1 and 8.0.3). An application that pins one of those lower directly will get NU1605 and needs to raise the pin. (#​4073)

The same fix ships for 4.x's Quartz.Dashboard.Agent in 4.5.1.

What's Changed

Other changes

Full Changelog: quartznet/quartznet@v3.22.5...v3.22.6

3.22.5

One fix for the 3.x line, ported from Quartz.NET 4.5. There is no public API change and no schema change.

Fixed

  • A calendar replacement that throws leaves the in-memory store as it was. RAMJobStore.StoreCalendar(name, calendar, replaceExisting: true, updateTriggers: true) moved each trigger on the calendar to the replacement one at a time. If the replacement threw for a trigger, three things went wrong:

    • that trigger dropped out of the schedule for good;
    • the triggers before it had already moved on;
    • the replacement calendar was already stored.

    Now every trigger is recomputed on a copy first. If one throws, the call fails with JobPersistenceException("Couldn't store calendar: …"), worded and wrapped as the database stores do, and nothing changes: the old calendar stays, and every trigger keeps its fire time and its place in the schedule. The failure is the caller's, so it does not count toward MaxConsecutiveFireFailures. (#​4039, the port of #​4029 that fixed #​4026)

The same fix ships in Quartz.NET 4.5.

Full Changelog: quartznet/quartznet@v3.22.4...v3.22.5

3.22.4

Fixes for the 3.x line. The public API gains one property, and there is no schema change. These are ports of fixes found while building Quartz.NET 4.4.

Fixed

  • A trigger whose fire fails every time is stored ERROR instead of being acquired again forever. A trigger whose fire failed on each attempt was released and acquired again in a tight loop, and starved its [DisallowConcurrentExecution] job's other triggers. Five consecutive failed fires of the same occurrence now store it ERROR; ResetTriggerFromErrorState brings it back. (#​3963)

  • A calendar that throws fails only its own trigger. An ICalendar that threw used to strand everything around it:

    • in the in-memory store, the whole fire batch (#​3974);
    • in the in-memory store, the acquisition pass and a completion that unblocks a serial job's triggers (#​3985);
    • in the database stores, a completion: it was retried until shutdown, the job stayed BLOCKED and the worker thread never returned (#​4006). The misfire handler also logged the same trigger on every scan.

    Now the trigger whose calendar threw is left as it was and counted as a failure. The rest of the batch, pass or completion carries on, and a database error is still retried as before.

New

  • JobStoreSupport.MaxConsecutiveFireFailures and RAMJobStore.MaxConsecutiveFireFailures (flat key quartz.jobStore.maxConsecutiveFireFailures), default 5; 0 turns parking off.

Behaviour changes

  • A trigger is parked ERROR after 5 consecutive failed fires. A calendar that keeps throwing while a misfire is handled parks its trigger after 5 failures that are at least a misfire threshold apart, not after 5 quick passes. Set MaxConsecutiveFireFailures = 0 to keep the old behaviour.
  • ResumeTrigger, ResumeTriggers, ResumeJob, ResumeJobs and ResumeAll no longer throw a calendar's exception. They log it and resume the trigger, and its misfire is handled again later.
  • The protected JobStoreSupport.UpdateMisfiredTrigger returns false instead of throwing when a misfire policy throws. It returns true when that failure stored the trigger ERROR.

The same fixes ship in Quartz.NET 4.4.

Full Changelog: quartznet/quartznet@v3.22.3...v3.22.4

Commits viewable in compare view.

Updated Quartz.Extensions.Hosting from 3.22.3 to 3.22.7.

Release notes

Sourced from Quartz.Extensions.Hosting's releases.

3.22.7

Fixes for the 3.x line, ported from 4.6. There is no public API change and no schema change.

Fixed

  • A trigger re-applied at startup keeps its previous fire time. Creating a scheduler re-applies the triggers the configuration registers through RescheduleJob, which replaced the stored trigger with one that had none, so PreviousFireTimeUtc was lost on every restart. It is now carried over when the replacement has none. (#​4127, from #​4122)
  • A recovered trigger keeps its job's execution group. A firing replayed after a node failure, a shutdown hand-back or startup recovery was stored ungrouped and ran beside a live firing of the same group, whatever the group's limit. (#​4085)
  • A manual firing carries the execution group its job's triggers share. TriggerJob and the dashboard's Trigger now carried none, so they ignored the group's limit. (#​4110)
  • Names in IConfiguration keep their case. A hierarchical section camel-cased every path segment on its way to the flat quartz.* keys, names the user chose included, and StdSchedulerFactory looks names up ordinally: Quartz:DataSource:MyDS beside Quartz:JobStore:DataSource = MyDS failed with no data source found. Data source, listener, execution-limit and context names now keep their case, and a plugin's name stays camel-cased, so the XML plugin's stored file-scan job keeps its key. (#​4108)
  • The dashboard's cron preview uses the trigger's time zone and calendar, and previews the expression being edited. (#​4118)

Warnings

  • A clustered scheduler warns when every node would share the instance id NON_CLUSTERED, which makes each node read the other's fired triggers as its own. Set quartz.scheduler.instanceId to AUTO, or a distinct id per node. 4.6 generates the id instead; 3.x keeps the default, because changing it would re-key an existing deployment's rows. (#​4106)
  • A generated job or trigger identity in a persistent store logs a warning: a generated key is new on every start, so a persistent store keeps another copy each time, and every copy of a trigger fires. Give it a stable key with WithIdentity. (#​4114)

What's Changed

Other changes

Full Changelog: quartznet/quartznet@v3.22.6...v3.22.7

3.22.6

One dependency fix for the 3.x line, from Microsoft's October 13 security advisories. There is no public API change and no schema change, and no other package changes.

Fixed

  • Quartz.Dashboard depends on Microsoft.AspNetCore.SignalR.Client 8.0.32. 3.22.5 depended on 8.0.8, whose Microsoft.AspNetCore.SignalR.Common GHSA-334f-vvp4-7g6p (CVE-2026-70159) covers, and 8.0.32 is the fixed version on the 8.x line. The fixed client raises Microsoft.Extensions.DependencyInjection, DependencyInjection.Abstractions, Logging and Logging.Abstractions within 8.0.x (to 8.0.1, 8.0.2, 8.0.1 and 8.0.3). An application that pins one of those lower directly will get NU1605 and needs to raise the pin. (#​4073)

The same fix ships for 4.x's Quartz.Dashboard.Agent in 4.5.1.

What's Changed

Other changes

Full Changelog: quartznet/quartznet@v3.22.5...v3.22.6

3.22.5

One fix for the 3.x line, ported from Quartz.NET 4.5. There is no public API change and no schema change.

Fixed

  • A calendar replacement that throws leaves the in-memory store as it was. RAMJobStore.StoreCalendar(name, calendar, replaceExisting: true, updateTriggers: true) moved each trigger on the calendar to the replacement one at a time. If the replacement threw for a trigger, three things went wrong:

    • that trigger dropped out of the schedule for good;
    • the triggers before it had already moved on;
    • the replacement calendar was already stored.

    Now every trigger is recomputed on a copy first. If one throws, the call fails with JobPersistenceException("Couldn't store calendar: …"), worded and wrapped as the database stores do, and nothing changes: the old calendar stays, and every trigger keeps its fire time and its place in the schedule. The failure is the caller's, so it does not count toward MaxConsecutiveFireFailures. (#​4039, the port of #​4029 that fixed #​4026)

The same fix ships in Quartz.NET 4.5.

Full Changelog: quartznet/quartznet@v3.22.4...v3.22.5

3.22.4

Fixes for the 3.x line. The public API gains one property, and there is no schema change. These are ports of fixes found while building Quartz.NET 4.4.

Fixed

  • A trigger whose fire fails every time is stored ERROR instead of being acquired again forever. A trigger whose fire failed on each attempt was released and acquired again in a tight loop, and starved its [DisallowConcurrentExecution] job's other triggers. Five consecutive failed fires of the same occurrence now store it ERROR; ResetTriggerFromErrorState brings it back. (#​3963)

  • A calendar that throws fails only its own trigger. An ICalendar that threw used to strand everything around it:

    • in the in-memory store, the whole fire batch (#​3974);
    • in the in-memory store, the acquisition pass and a completion that unblocks a serial job's triggers (#​3985);
    • in the database stores, a completion: it was retried until shutdown, the job stayed BLOCKED and the worker thread never returned (#​4006). The misfire handler also logged the same trigger on every scan.

    Now the trigger whose calendar threw is left as it was and counted as a failure. The rest of the batch, pass or completion carries on, and a database error is still retried as before.

New

  • JobStoreSupport.MaxConsecutiveFireFailures and RAMJobStore.MaxConsecutiveFireFailures (flat key quartz.jobStore.maxConsecutiveFireFailures), default 5; 0 turns parking off.

Behaviour changes

  • A trigger is parked ERROR after 5 consecutive failed fires. A calendar that keeps throwing while a misfire is handled parks its trigger after 5 failures that are at least a misfire threshold apart, not after 5 quick passes. Set MaxConsecutiveFireFailures = 0 to keep the old behaviour.
  • ResumeTrigger, ResumeTriggers, ResumeJob, ResumeJobs and ResumeAll no longer throw a calendar's exception. They log it and resume the trigger, and its misfire is handled again later.
  • The protected JobStoreSupport.UpdateMisfiredTrigger returns false instead of throwing when a misfire policy throws. It returns true when that failure stored the trigger ERROR.

The same fixes ship in Quartz.NET 4.4.

Full Changelog: quartznet/quartznet@v3.22.3...v3.22.4

Commits viewable in compare view.

Updated SQLitePCLRaw.lib.e_sqlite3 from 2.1.13 to 2.1.14.

Release notes

Sourced from SQLitePCLRaw.lib.e_sqlite3's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated StackExchange.Redis from 3.3.1 to 3.4.5.

Release notes

Sourced from StackExchange.Redis's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Swashbuckle.AspNetCore from 10.2.3 to 10.3.1.

Release notes

Sourced from Swashbuckle.AspNetCore's releases.

10.3.1

What's Changed

Deprecations

[!IMPORTANT]
Swashbuckle.AspNetCore.ApiTesting.Xunit depended on Xunit v2, which is no longer supported.

The package has been removed and no further versions will be released.

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.3.0...v10.3.1

10.3.0

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.3...v10.3.0

Commits viewable in compare view.

Updated Temporalio from 1.20.0 to 1.21.0.

Release notes

Sourced from Temporalio's releases.

1.21.0

Notable Changes

💥 Breaking Changes

  • Core: Replay detects changes to the service or operation of scheduled Nexus operations, reporting nondeterminism while retaining compatibility with histories recorded before these checks.
  • SchedulePolicy.CatchupWindow is now nullable and defaults to null. An unspecified window uses the server configured default.

Added

  • Added experimental Event Groups: Workflow.CreateEventGroup groups related history events for UI and observability using a required ID (used verbatim; omit secrets) and an optional codec-encoded label. Attach groups with Workflow.WithEventGroups or command-option EventGroups; signal and update handlers receive implicit inbound groups.
  • Added OpenTelemetryOptions.HistogramAggregation, which can be set to OpenTelemetryHistogramAggregation.Base2Exponential to export OTLP histograms, including custom ones, as OpenTelemetry exponential histograms, which Prometheus-compatible backends store as native histograms. Each series gets a name suffix (_native by default) so it never collides with the fixed-bucket series it replaces; this mode cannot be combined with HistogramBucketOverrides.
  • Added experimental Endpoint, Operation, and Service properties to the NexusOperationHandle class.
  • Added experimental ISerializationContext.Nexus support for callers' inputs, results, failures, and user metadata, and handlers' inputs, synchronous results, and failures. Standalone handles use the start request's context, including already-running operations; asynchronous-operation results and handles obtained through GetNexusOperationHandle with only an operation ID do not use this context.
  • Add experimental ChildWorkflowOptions.VersioningOverride for pinned, auto-upgrade, and one-time child workflow routing independently of the parent (Temporal Server 1.32.0+), VersioningOverride.OneTime for one-time routing on both client and child workflow starts, and InvalidVersioningOverrideException for invalid child overrides.
  • DevServerOptions.StartupTimeout and TestServerOptions.StartupTimeout set how long a local or time-skipping WorkflowEnvironment waits for its server to become ready, excluding download time. The default remains five seconds.
  • Added WorkflowInfo.OriginalExecutionRunId, the run ID recorded on the workflow execution started event. Unlike RunId, this value is preserved across workflow resets.

Stabilized

  • Removed experimental warnings from the core plugin APIs and client/worker plugin options.
  • DevServerOptions and TestServerOptions are no longer marked unstable. They remain specific to the dev server and test server implementations and may no longer be valid if those change.

Fixed

  • Fixed an exception when reading schedule policies with an unset catchup window.
  • Core: A workflow task that arrives while a workflow waits on a local activity, such as a legacy query, now waits until the current workflow task is reported. Previously it replaced that workflow task ("Trying to send a new WFT for a run which already has one!"), which then timed out on the server and could leave the workflow stuck on a nondeterminism error.
  • Fixed update validators being skipped when a typed client update call populated the cache before the workflow definition was created in the same process.
  • Core: Worker heartbeats now report correct task-slot and poller counts when using buffered or custom metrics backends, including the .NET SDK's CustomMetricMeter. Previously these counts could remain 0 because heartbeat accounting depended on reading labels from backend-owned attributes.
  • Core: Local activities still running when their workflow is evicted or the worker shuts down now always receive a cancellation. Local activities no longer retry ordinary failures or start-to-close timeouts after cancellation has been requested, matching non-local activities. Workflow code no longer observes a spurious local activity cancellation when its run is evicted or completes while the local activity is backing off between retries.
  • Core: Workers no longer panic when evicting a workflow with buffered local activity results. Completed activations' output is recorded before eviction, without recording eviction-induced cancellations.
  • Unexpected errors in workflow-internal tasks for child workflows and updates, such as a failure converter throwing while resolving a child workflow, now fail the workflow task instead of being silently lost. For queries, such errors fail only the query itself, not the workflow task.
  • Core: Workers now replay workflows paused before a scheduled task starts, allowing those workflows to make progress after unpause.
  • Source Link in the published symbol packages now resolves every source file, and packages are built with normalized paths so they are reproducible.
  • Temporalio.Extensions.DiagnosticSource.CustomMetricMeter no longer throws when a tag is appended with a key that the tag set already has. The appended value now replaces the existing one.
  • Core: Replay now preserves which local activity results were delivered together for newly recorded histories. This prevents local activity scheduling which was conditional on local activity resolution order from assigning recorded results to different handles. Older markers keep their existing behavior.
  • TemporalWorkerService created with the TemporalWorkerServiceOptions constructor now connects using ClientOptions and honors WorkerClientUpdater. Previously it failed with a NullReferenceException when started.
  • Prevented use-after-free errors caused by early finalization of Temporalio.Bridge.ByteArray.
  • Core: Dev and test server startup now stops waiting at the configured deadline even if a readiness request stalls. Timeout messages include the last connection failure when available.
  • Core: Workers with large workflow caches avoid unnecessary CPU usage when no workflow tasks are waiting for a cache slot.
  • An activity started using the ambient TemporalClient directly from inside a synchronous Nexus operation handler now inherits the handler's request ID and inbound links, same as the guarded start already gets.

Security

SDK Core Commits

Commits viewable in compare view.

Updated Testcontainers.CosmosDb from 4.15.0 to 4.16.0.

Release notes

_Sourced from [Testcontain...

_Description has been t...

Description has been truncated

@dependabot
Bump the minor-and-patch group with 23 updates
5b75333 
Bumps Aspire.Hosting.AppHost from 13.5.4 to 13.6.2
Bumps Aspire.Hosting.Azure.CosmosDB from 13.5.4 to 13.6.2
Bumps bunit from 2.11.3 to 2.12.5
Bumps Microsoft.Azure.Cosmos from 3.63.1 to 3.63.2
Bumps Microsoft.Data.SqlClient from 7.1.0 to 7.1.1
Bumps Microsoft.Data.Sqlite from 10.0.12 to 10.0.13
Bumps Microsoft.Extensions.AI.Abstractions from 10.10.1 to 10.11.0
Bumps Microsoft.Extensions.Http from 10.0.12 to 10.0.13
Bumps Microsoft.NET.Test.Sdk from 18.10.1 to 18.11.0
Bumps ModelContextProtocol from 2.2.0 to 2.3.0
Bumps ModelContextProtocol.AspNetCore from 2.2.0 to 2.3.0
Bumps Quartz.Extensions.DependencyInjection from 3.22.3 to 3.22.7
Bumps Quartz.Extensions.Hosting from 3.22.3 to 3.22.7
Bumps SQLitePCLRaw.lib.e_sqlite3 from 2.1.13 to 2.1.14
Bumps StackExchange.Redis from 3.3.1 to 3.4.5
Bumps Swashbuckle.AspNetCore from 10.2.3 to 10.3.1
Bumps Temporalio from 1.20.0 to 1.21.0
Bumps Testcontainers.CosmosDb from 4.15.0 to 4.16.0
Bumps Testcontainers.MsSql from 4.15.0 to 4.16.0
Bumps Testcontainers.PostgreSql from 4.15.0 to 4.16.0
Bumps Testcontainers.Redis from 4.15.0 to 4.16.0
Bumps xunit.runner.visualstudio from 4.0.0 to 4.0.1
Bumps xunit.v3 from 4.0.1 to 4.0.2

---
updated-dependencies:
- dependency-name: Aspire.Hosting.AppHost
  dependency-version: 13.6.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Aspire.Hosting.Azure.CosmosDB
  dependency-version: 13.6.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: bunit
  dependency-version: 2.12.5
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Microsoft.Azure.Cosmos
  dependency-version: 3.63.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: Microsoft.Data.SqlClient
  dependency-version: 7.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: Microsoft.Data.Sqlite
  dependency-version: 10.0.13
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: Microsoft.Extensions.AI.Abstractions
  dependency-version: 10.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Microsoft.Extensions.Http
  dependency-version: 10.0.13
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: ModelContextProtocol
  dependency-version: 2.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: ModelContextProtocol.AspNetCore
  dependency-version: 2.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Quartz.Extensions.DependencyInjection
  dependency-version: 3.22.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: Quartz.Extensions.Hosting
  dependency-version: 3.22.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: SQLitePCLRaw.lib.e_sqlite3
  dependency-version: 2.1.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: StackExchange.Redis
  dependency-version: 3.4.5
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Swashbuckle.AspNetCore
  dependency-version: 10.3.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Temporalio
  dependency-version: 1.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Testcontainers.CosmosDb
  dependency-version: 4.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Testcontainers.MsSql
  dependency-version: 4.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Testcontainers.PostgreSql
  dependency-version: 4.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Testcontainers.Redis
  dependency-version: 4.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: xunit.runner.visualstudio
  dependency-version: 4.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: xunit.v3
  dependency-version: 4.0.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from ivanvyd as a code owner October 21, 2026 20:05
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ivanvyd ivanvyd Awaiting requested review from ivanvyd ivanvyd is a code owner

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

0 participants