Skip to content

chore(deps): Bump AWSSDK.S3 and 14 others - #81

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/nuget-menores-bdb25c7f7b
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/nuget-menores-bdb25c7f7b

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Pinned AWSSDK.S3 at 4.1.1.

Release notes

Sourced from AWSSDK.S3's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated coverlet.collector from 10.1.0 to 10.1.1.

Release notes

Sourced from coverlet.collector's releases.

10.1.1

Improvements

  • Add IsReachable to branch points, computed from the method's control-flow graph, and exclude unreachable branches from branch-coverage totals and from branch details in Cobertura, LCOV and OpenCover reports #​2056 by @​pcshrosbree
  • coverlet.MTP: Narrow Dynamic Exclude Filters for Loaded Assemblies #​2069

Fixed

  • Fix Regression Prevent invalid IL from branch trampolines #​2067
  • Fix Regression coverlet.MTP does not instrument local functions #​2046

Maintenance

  • Update NuGet package versions #​2050

Diff between 10.1.0 and 10.1.1

Commits viewable in compare view.

Pinned Fido2 at 4.3.3.

Release notes

Sourced from Fido2's releases.

4.3.3

What's Changed

Full Changelog: passwordless-lib/fido2-net-lib@4.3.2...4.3.3

Commits viewable in compare view.

Pinned JasperFx.Events at 2.102.0.

Release notes

Sourced from JasperFx.Events's releases.

2.102.0

JasperFx 2.102.0 is a minor release with one new IEventDatabase capability. It lets monitoring report projection lag as time rather than as a count of events.

  • IEventDatabase.FetchFirstEventTimestampsAfterAsync, the age of the oldest unprocessed event (#​1150 / #​1151).
    • Why: a backlog counted in events says little on a multi-tenant fleet. 40,000 events spread over 130 tenants is fine; 40,000 on one tenant for an hour is not. The age of the oldest event a shard hasn't processed tells those two apart, and it's the number an SLO is written against. CritterWatch reaches event stores only through the JasperFx.Events abstractions, so the question has to be answerable here.
    • What it answers: for each (TenantId, Sequence) position, it returns the store's timestamp of the first event with a higher sequence, or null when there is none (the shard is caught up). You get one PendingEventAge(TenantId, Sequence, Timestamp) per position, in the order asked. PendingEventAge also has IsCaughtUp and AgeAt(now), which never returns a negative age when clocks are skewed.
    • Tenants: a null tenant considers every event in the database. A non-null tenant considers only that tenant's events under conjoined tenancy or per-tenant partitioning.
    • Archived events don't count. The async daemon skips them, so a shard is never waiting on one.
    • Cost: stores answer the whole list in one round trip per database, with one sequence seek per position, never a scan or a count. Ask only about shards that are behind.
    • Default implementations: the batched member throws NotSupportedException on a store that hasn't implemented it. A null timestamp means "caught up", so that default can't answer without reporting a lagging shard as current. The single-position convenience FetchFirstEventTimestampAfterAsync(sequence, tenantId) calls the batched member by default. The in-memory prototyping store implements both.
  • Compliance: a new PendingEventAgeCompliance suite, gated by SupportsPendingEventAges (default false), with 12 facts. They cover the "strictly after" rule, ordering and duplicates, archived events and conjoined tenant scoping. A new SupportsStreamArchiving fixture flag (default true) gates the archived facts. Stores must enroll the new suite (or excuse it) or ComplianceSuiteInventory.AssertEnrolled fails.

Marten, Polecat and Fisher implement the method in their JasperFx 2.102.0 upgrades.

What's Changed

Full Changelog: JasperFx/jasperfx@v2.101.1...v2.102.0

2.101.1

JasperFx 2.101.1 is a patch release with one fix.

  • Overlapping StopAsync / PauseAsync calls on the projection coordinator no longer throw ObjectDisposedException (#​1148 / #​1149).
    • What was broken: ProjectionCoordinatorBase read, awaited across, then disposed and replaced its shared cancellation source and runner with nothing serializing callers. Two stops in flight at once could cancel a source the other had just disposed. Two starts in flight at once could each build a leadership loop, leaving one running that nothing would ever cancel.
    • When it happened: JasperFx's RunCommand stops the host again when ApplicationStopping fires, so tests hosting an app through WebApplicationFactory or Alba had two IHost.StopAsync calls racing at teardown.
    • How it works now: start, pause and stop are serialized, so overlapping calls behave like sequential ones: the first stop tears down and the rest find nothing left to do. Marten's and Polecat's ProjectionCoordinator pick this up from the base class. Marten's ExplicitProjectionCoordinator has its own fix in JasperFx/marten#​5843.
  • CI: concurrency stress tests now live in a separate StressTests project that runs its tests one at a time, so they can't starve timing-sensitive tests of thread-pool threads.

What's Changed

Full Changelog: JasperFx/jasperfx@v2.101.0...v2.101.1

Commits viewable in compare view.

Updated JasperFx.Events.SourceGenerator from 2.101.0 to 2.102.0.

Release notes

Sourced from JasperFx.Events.SourceGenerator's releases.

2.102.0

JasperFx 2.102.0 is a minor release with one new IEventDatabase capability. It lets monitoring report projection lag as time rather than as a count of events.

  • IEventDatabase.FetchFirstEventTimestampsAfterAsync, the age of the oldest unprocessed event (#​1150 / #​1151).
    • Why: a backlog counted in events says little on a multi-tenant fleet. 40,000 events spread over 130 tenants is fine; 40,000 on one tenant for an hour is not. The age of the oldest event a shard hasn't processed tells those two apart, and it's the number an SLO is written against. CritterWatch reaches event stores only through the JasperFx.Events abstractions, so the question has to be answerable here.
    • What it answers: for each (TenantId, Sequence) position, it returns the store's timestamp of the first event with a higher sequence, or null when there is none (the shard is caught up). You get one PendingEventAge(TenantId, Sequence, Timestamp) per position, in the order asked. PendingEventAge also has IsCaughtUp and AgeAt(now), which never returns a negative age when clocks are skewed.
    • Tenants: a null tenant considers every event in the database. A non-null tenant considers only that tenant's events under conjoined tenancy or per-tenant partitioning.
    • Archived events don't count. The async daemon skips them, so a shard is never waiting on one.
    • Cost: stores answer the whole list in one round trip per database, with one sequence seek per position, never a scan or a count. Ask only about shards that are behind.
    • Default implementations: the batched member throws NotSupportedException on a store that hasn't implemented it. A null timestamp means "caught up", so that default can't answer without reporting a lagging shard as current. The single-position convenience FetchFirstEventTimestampAfterAsync(sequence, tenantId) calls the batched member by default. The in-memory prototyping store implements both.
  • Compliance: a new PendingEventAgeCompliance suite, gated by SupportsPendingEventAges (default false), with 12 facts. They cover the "strictly after" rule, ordering and duplicates, archived events and conjoined tenant scoping. A new SupportsStreamArchiving fixture flag (default true) gates the archived facts. Stores must enroll the new suite (or excuse it) or ComplianceSuiteInventory.AssertEnrolled fails.

Marten, Polecat and Fisher implement the method in their JasperFx 2.102.0 upgrades.

What's Changed

Full Changelog: JasperFx/jasperfx@v2.101.1...v2.102.0

2.101.1

JasperFx 2.101.1 is a patch release with one fix.

  • Overlapping StopAsync / PauseAsync calls on the projection coordinator no longer throw ObjectDisposedException (#​1148 / #​1149).
    • What was broken: ProjectionCoordinatorBase read, awaited across, then disposed and replaced its shared cancellation source and runner with nothing serializing callers. Two stops in flight at once could cancel a source the other had just disposed. Two starts in flight at once could each build a leadership loop, leaving one running that nothing would ever cancel.
    • When it happened: JasperFx's RunCommand stops the host again when ApplicationStopping fires, so tests hosting an app through WebApplicationFactory or Alba had two IHost.StopAsync calls racing at teardown.
    • How it works now: start, pause and stop are serialized, so overlapping calls behave like sequential ones: the first stop tears down and the rest find nothing left to do. Marten's and Polecat's ProjectionCoordinator pick this up from the base class. Marten's ExplicitProjectionCoordinator has its own fix in JasperFx/marten#​5843.
  • CI: concurrency stress tests now live in a separate StressTests project that runs its tests one at a time, so they can't starve timing-sensitive tests of thread-pool threads.

What's Changed

Full Changelog: JasperFx/jasperfx@v2.101.0...v2.101.1

Commits viewable in compare view.

Pinned Marten at 9.62.0.

Release notes

Sourced from Marten's releases.

9.62.0

Marten 9.62.0 is a small bug-fix release on Weasel 9.51.0.

Fixes

  • HiLo SetFloor() can no longer be undone by an id fetch already in progress (#​5998). Before this release, a NextLong() that had already reserved its next block could finish installing it after SetFloor(n) returned. That handed out ids below the new floor, and under the same race an id could also be issued twice. SetFloor() now waits for that fetch and installs its own block after it. The fix is in Weasel 9.51.0 (weasel#​849, weasel#​853); there's no Marten code change.
  • Single instance tenancy no longer starves the thread pool on a tenant's first synchronous session (#​5985). GetTenant() for an uncached tenant now checks for the tenant's database, and runs CREATE DATABASE when it's missing, with synchronous I/O on the calling thread. It used to block on the async path. The exception is a Multiplexing master connection, which Npgsql only supports asynchronously. Together with 9.61.0, all three per-tenant database tenancies (master table, single instance, sharded) now resolve known tenants without sync-over-async.

No schema changes. Weasel goes from 9.50.0 to 9.51.0 (additive). JasperFx stays at 2.102.0.

What's Changed

Full Changelog: JasperFx/marten@V9.61.0...V9.62.0

9.61.0

Marten 9.61.0 is a bug-fix release for multi-tenancy. Its two themes are synchronous tenant resolution under load and sharded tenant assignments.

Behaviour change (see the migration guide, "Key Changes in 9.61.0", on the 9.0 branch)

  • Sharded tenancy never reassigns a tenant that already has a shard (#​5995). A store that hadn't loaded the database pool could re-run the assignment strategy for an already-assigned tenant. It then overwrote the assignment, moving the tenant to another shard while its data stayed on the old one. Two processes racing to assign the same new tenant could also end up on different shards. An existing assignment is now final. If the assigned shard is missing from the pool, Marten throws the new Marten.Exceptions.AssignedShardNotFoundException (TenantId, DatabaseId) and doesn't reassign the tenant.

Fixes

  • No more thread-pool starvation on the first synchronous session for a tenant. The synchronous session factories and ForTenant(tenantId) resolve a tenant that isn't cached yet. They used to do that with sync-over-async, so a burst of first sessions for new tenants could stall the whole process. That burst is typical right after a deploy.
    • Master table tenancy reads the tenant's row with synchronous I/O (#​5985). The exception is a Multiplexing control database, which Npgsql only supports asynchronously.
    • Sharded tenancy resolves a tenant that already has its shard, partitions and event sequence with synchronous I/O (#​5986). New tenants, repairs and the first resolution in a process still take the async path.
    • Single instance tenancy isn't fixed yet. The guidance is in the multi-tenancy docs: warm known tenants at startup, or resolve a new tenant with GetTenantAsync() before its first synchronous session.

Repository and test-only

  • The test harness's Dispose tolerates a half-built context (#​5976), and a MultiHostTests standby-replay fix (#​5979).
  • CI now runs tests.yml and the docs checks on pull requests and pushes to 9.0 (#​5977).

No schema changes and no dependency changes: JasperFx 2.102.0 and Weasel 9.50.0, as in 9.60.0.

What's Changed

Full Changelog: JasperFx/marten@V9.60.0...V9.61.0

9.60.0

Marten 9.60.0 is a bug-fix release, mostly for LINQ correctness. Several queries that silently returned wrong results now return what LINQ to Objects returns. Shapes Marten can't translate exactly now throw BadLinqExpressionException instead of returning the wrong rows.

Behaviour changes (see the migration guide, "Key Changes in 9.60.0")

  • LINQ Count() after Take()/Skip() counts the page. Skip(k).Take(n).Count() used to return 0, and Take(n).Count() the full count (#​5920).
  • LINQ Take()/Skip() before SelectMany() pages the parent documents, not the flattened rows (#​5928).
  • LINQ Select() after SelectMany() projects the flattened rows. The projection used to be silently dropped (#​5933).
  • LINQ ordering:
    • A second OrderBy() re-sorts the results, as LINQ does (#​5959).
    • Computed keys such as OrderBy(x => -x.Number) are computed, including over child documents and joins, or refused. They used to sort by the underlying member (#​5957, #​5968).
    • OrderBy() after a projection orders the projected values (#​5955).
  • LINQ indexes into document arrays translate in OrderBy/Select/jagged Where. A negative index now throws (#​5949).
  • A failed save reports the failing operation's exception. A FetchForWriting() version conflict in the same save as a StartStream() now throws EventStreamUnexpectedMaxEventIdException (a ConcurrencyException) instead of a wrong ExistingStreamIdCollisionException (#​5914).
  • DCB: a boundary save no longer conflicts with boundaries it didn't change. There's also an opt-in scope that conflicts by event type (#​5887).

Schema change

  • mt_get_next_hi is now an atomic increment (#​5938). Under concurrent load, HiLo could use up its retry limit and throw HiloSequenceAdvanceToNextHiAttemptsExceededException. The function body changes, so your next schema migration applies it. Until then the old function keeps working.

Other fixes

  • The async daemon loads events from the primary under ReadSessionPreference, so a lagging standby can no longer make it skip events (#​5888).
  • A session no longer leaks a pooled connection when BeginTransactionAsync is cancelled or fails (#​5881).
  • A HiLo type's first burst of synchronous Store() calls no longer stalls the process through thread-pool starvation (#​5969).
  • More LINQ shapes now work:
    • First/Single after SelectMany (#​5921)
    • Any() over a GroupJoin
    • SelectMany over duplicated arrays (#​5934) and enum arrays (#​5940)
    • string Length after SelectMany (#​5941)
    • computed top-level Select() (#​5942)
    • static members and array indexing inside predicates (#​5943)
    • ordering by a value that reads nothing from the document (#​5950)

What's Changed

9.59.0

Marten 9.59.0 moves to JasperFx 2.102.0 and Weasel 9.50.0. It adds read-only DCB tag queries on a query session, reports how old a projection's oldest unprocessed event is, and fixes a shutdown race in the explicit projection coordinator.

Highlights

  • DCB tag queries through a query session: EventsExistAsync, QueryByTagsAsync and AggregateByTagsAsync are now on IQuerySession.Events, so a read-only endpoint no longer needs a document session to read by tags (thanks to new contributor @​alekbarszczewski, #​5841). FetchForWritingByTags still needs a document session. Existing calls through IDocumentSession.Events are unchanged, both in source and in compiled assemblies. A class that implements Marten.Events.IQueryEventStore itself has three more members to implement.
  • Pending event ages: Marten implements JasperFx 2.102.0's IEventDatabase.FetchFirstEventTimestampsAfterAsync. It returns the timestamp of the oldest event a shard hasn't processed yet, in one round trip. CritterWatch uses it to report projection lag as time instead of a count of events (#​5844).
  • Explicit projection coordinator shutdown race: overlapping StopAsync / PauseAsync calls, such as the second stop JasperFx's RunCommand issues when WebApplicationFactory or Alba stops the host, no longer stop and dispose the same daemons twice or log "Error while trying to stop daemon agents". A start that overlaps a stop no longer starts a disposed daemon, and a daemon resolved during a stop is no longer dropped without being disposed (#​5842, #​5843).
  • The command line under Native AOT: JasperFx 2.101.0 runs the command line from a Native AOT binary, and with Weasel 9.50.0 the db-* commands (db-apply, db-assert, db-patch, db-dump, db-list) now appear and run there too. JIT applications see no change (#​5840, #​5845).
  • Docs: schema management now explains when to use lazy AutoCreate, apply at startup, db-apply / resources setup as a deployment step, or db-patch scripts for a DBA, with links to the Weasel CLI and JasperFx stateful resource docs (#​5839).

What's Changed

New Contributors

Full Changelog: JasperFx/marten@v9.58.0...V9.59.0

Commits viewable in compare view.

Pinned Microsoft.AspNetCore.Authentication.JwtBearer at 10.0.15.

Release notes

Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.OpenApi from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.AspNetCore.OpenApi's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Data.SqlClient from 6.1.1 to 6.1.8.

Release notes

Sourced from Microsoft.Data.SqlClient's releases.

6.1.8

This update brings the following changes since the 6.1.7 release:

Changed

  • Updated the System.Security.Cryptography.Pkcs dependency to 8.0.2 (was 8.0.1) for .NET Framework 4.6.2, .NET 8.0, and .NET Standard 2.0, and updated the Microsoft.Extensions.Caching.Memory, System.Configuration.ConfigurationManager, and System.Security.Cryptography.Pkcs dependencies to 9.0.21 (was 9.0.11) for .NET 9.0.
    (#​4842, #​4862, #​4870)

  • Improved the error reported when Active Directory Interactive authentication through the Windows Web Account Manager (WAM) broker fails because the host has no parent window, such as a service or Azure Functions host. The resulting error now explains the supported alternatives: supply a parent window with SetParentActivityOrWindowFunc, use Active Directory Default with a configured non-interactive credential, or supply a custom ApplicationClientId with UseWamBroker disabled. The original MSAL error code and inner exception are preserved, and authentication selection, retry behavior, and other failures are unchanged. (Windows only)
    (#​4854, #​4858, #​4918)

Fixed

  • Fixed the managed SNI path ignoring HostNameInCertificate during server certificate validation. When HostNameInCertificate is set, it is now the only host name the server certificate is validated against, and certificates that do not match it are rejected. Default host-name selection when the property is not set, certificate chain validation, ServerCertificate matching, and the connection destination are unchanged. (net8.0/net9.0 only)
    (#​4905, #​4909)

  • Fixed Always Encrypted enclave session caching so that cached enclave sessions are isolated by attestation protocol. A session established with one Attestation Protocol setting is no longer reused by a connection to the same server, database, and attestation URL that uses a different protocol.
    (#​4829, #​4868)

  • Fixed SqlDataReader.HasRows returning false when a result set contains rows but the server sends multiple informational messages, or an informational message before an ORDER token, ahead of the first row. Empty results still report false, and InfoMessage delivery is unchanged.
    (#​3018, #​4773, #​4898)

  • Fixed an intermittent InvalidOperationException ("Nullable object must have a value") from statistics bookkeeping when commands complete concurrently on a MARS connection. This issue was reported as a regression starting with 6.1.4.
    (#​4778, #​4875, #​4896)

  • Fixed Entra ID authentication when the server supplies an authority URL with an OAuth endpoint suffix, such as https://login.microsoftonline.com/<tenant>/oauth2/authorize returned by the Dataverse/Dynamics 365 TDS endpoint. The provider now extracts the tenant from the first path segment and uses the normalized authority for Azure.Identity credentials, MSAL, and their cache keys. An authority URL that cannot be parsed now fails with a clear, localized ArgumentException naming the authority. Bare tenant authority URLs used by Azure SQL and Fabric retain their existing behavior.
    (#​4496, #​4521, #​4791, #​4807)

Target Platform Support

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

Full details: release-notes/6.1/6.1.8.md

6.1.7

This update brings the following changes since the 6.1.6 release:

Changed

  • Updated the Microsoft.Data.SqlClient.SNI and Microsoft.Data.SqlClient.SNI.runtime dependencies to 6.0.3 (was 6.0.2).
    (#​4598)

Fixed

  • Fixed ServerCertificate validation on the managed SNI path so the configured certificate is compared against the server certificate even when the server certificate passes chain and host-name validation. When certificate validation is enabled, a missing, unreadable, or invalid certificate file, a certificate mismatch, or a missing server certificate now causes the TLS handshake to fail instead of bypassing the configured certificate check. (net8.0/net9.0 only)
    (#​4445, #​4584)

  • Fixed Always Encrypted VSM/HGS enclave attestation to verify that the enclave public key used to establish a session matches the key committed to by the signed attestation report. Missing, malformed, or mismatched key-binding data now causes attestation to fail before the session secret is derived.
    (#​4532, #​4552)

  • Fixed SqlConnection.AccessTokenCallback not disabling Transparent Network IP Resolution by default, making it consistent with SqlConnection.AccessToken. An explicitly configured TransparentNetworkIPResolution connection-string value still takes precedence. (net462 only)
    (#​4520, #​4560)

  • Fixed token authentication state handling so clearing SqlConnection.AccessToken preserves an existing AccessTokenCallback in the connection pool key, and clearing AccessTokenCallback preserves an existing AccessToken. Callback-based authentication now also follows the same prelogin server-certificate validation rules as an explicitly supplied access token.
    (#​4520, #​4560)

  • Fixed configurable retry logic installing a permanent, process-wide assembly-resolution handler that could interfere with unrelated assembly loading. The handler is now active only while an explicitly configured custom retry provider is resolved and constructed, and probes AppContext.BaseDirectory instead of the current working directory. Place custom retry assemblies in the application base directory; dependencies loaded after provider construction must be resolvable through normal application dependency resolution or an application-provided handler. (net8.0/net9.0 only)
    (#​2214, #​4547, #​4664)

Target Platform Support

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

Full details: release-notes/6.1/6.1.7.md

6.1.6

This update brings the following changes since the 6.1.5 release:

Added

WAM broker support for the supported Entra ID authentication modes (Windows only)

What Changed:

  • Added support for the Web Account Manager (WAM) broker for the supported Microsoft Entra ID authentication modes. A new ActiveDirectoryAuthenticationProviderOptions options bag and a corresponding ActiveDirectoryAuthenticationProvider(ActiveDirectoryAuthenticationProviderOptions options) constructor were introduced, exposing a UseWamBroker property (alongside ApplicationClientId and DeviceCodeFlowCallback).
    (#​4288, #​4387)
  • Added a cross-platform SetParentActivityOrWindowFunc(Func<object> parentActivityOrWindowFunc) method so callers can supply a parent window handle on Windows or a parent Activity/UIViewController on Android/iOS/MAUI.

Who Benefits:

  • Applications using ActiveDirectoryInteractive and other supported Entra ID authentication modes on Windows benefit from the WAM broker's improved security (tokens are brokered by the OS), single sign-on with the logged-in Windows account, and support for Conditional Access and Windows Hello.

Impact:

  • When you supply your ApplicationClientId, WAM is opt-in via ActiveDirectoryAuthenticationProviderOptions.UseWamBroker. Consider enabling it when you want OS-brokered tokens, single sign-on with the signed-in Windows account, Windows Hello, and Conditional Access support.
  • UseWamBroker is a Windows-only setting and has no effect on non-Windows platforms, where interactive Entra ID flows always use the system browser.
  • Prefer the new options-bag constructor over the positional-argument overloads in new code.
var options = new ActiveDirectoryAuthenticationProviderOptions
{
    ApplicationClientId = "<your-app-client-id>",
    // Enable WAM (Windows only) for OS-brokered tokens, SSO, Windows Hello, and Conditional Access.
    UseWamBroker = true,
};
var provider = new ActiveDirectoryAuthenticationProvider(options);
// Supply the parent window/activity that owns the interactive sign-in prompt.
provider.SetParentActivityOrWindowFunc(() => parentWindowHandle);
SqlAuthenticationProvider.SetProvider(SqlAuthenticationMethod.ActiveDirectoryInteractive, provider);

Changed

Hardened TDS token parsing with data-length bounds checks

What Changed:

  • Added bounds checking when parsing TDS token data lengths. The parser now validates the declared length of incoming token data against the available buffer before reading, rejecting malformed or out-of-range length values instead of reading past the intended boundary.
    (#​4340, #​4359)

Who Benefits:

  • All consumers benefit from improved resilience against malformed or hostile TDS responses. A server (or man-in-the-middle) sending an invalid token length can no longer drive the parser to read beyond the declared payload.

Impact:
... (truncated)

6.1.5

This update brings the following changes since the 6.1.4 release:

Fixed

  • Fixed a connection performance regression where SPN (Service Principal Name) generation was triggered for non-integrated authentication modes (e.g., SQL authentication) on the native SNI path, causing unnecessary DNS lookups and significantly slower connection times. Only affects .NET on Windows (not .NET Framework). (#​3523, #​3946)
  • Fixed ExecuteScalar to properly propagate errors when the server sends data followed by an error token. Previously, errors such as conversion failures during WHERE clause evaluation were silently consumed during SqlDataReader.Close() instead of being thrown to the caller, which could result in transactions being unexpectedly zombied. (#​3736, #​3947)
  • Fixed SqlDataReader.GetFieldType and SqlDataReader.GetProviderSpecificFieldType to return the correct type (SqlVector<float>) for vector float32 columns. Previously, these methods did not follow the same type-resolution logic as GetValue, returning an incorrect type for vector columns. (#​4104, #​4151)

Target Platform Support

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

Dependencies

.NET Framework 4.6.2

  • Azure.Core 1.50.0
  • Azure.Identity 1.17.1
  • Microsoft.Data.SqlClient.SNI 6.0.2
  • Microsoft.Extensions.Caching.Memory 8.0.1
  • Microsoft.Identity.Client 4.80.0
  • Microsoft.IdentityModel.JsonWebTokens 7.7.1
  • Microsoft.IdentityModel.Protocols.OpenIdConnect 7.7.1
  • System.Buffers 4.6.1
  • System.Data.Common 4.3.0
  • System.Diagnostics.DiagnosticSource 8.0.1
  • System.IdentityModel.Tokens.Jwt 7.7.1
  • System.Memory 4.6.3
  • System.Security.Cryptography.Pkcs 8.0.1
  • System.Text.Json 8.0.6
  • System.Text.RegularExpressions 4.3.1

.NET 8.0

  • Azure.Core 1.50.0
  • Azure.Identity 1.17.1
  • Microsoft.Data.SqlClient.SNI.runtime 6.0.2
  • Microsoft.Extensions.Caching.Memory 8.0.1
  • Microsoft.Identity.Client 4.80.0
  • Microsoft.IdentityModel.JsonWebTokens 7.7.1
  • Microsoft.IdentityModel.Protocols.OpenIdConnect 7.7.1
  • Microsoft.SqlServer.Server 1.0.0
  • System.Configuration.ConfigurationManager 8.0.1
  • System.Diagnostics.DiagnosticSource 8.0.1
  • System.IdentityModel.Tokens.Jwt 7.7.1
  • System.Security.Cryptography.Pkcs 8.0.1

.NET 9.0

... (truncated)

6.1.4

This update brings the following changes since the 6.1.3 release:

Fixed

  • Fixed NullReferenceException issue with SqlDataAdapter when processing batch scenarios where certain SQL RPC calls may not include system parameters.
    (#​3877)
  • Fixed connection pooling issue where extra connection deactivation was causing active connection counts to go negative.
    (#​3776)

Added

AppContext Switch for enabling MultiSubnetFailover

What Changed:

  • Added new AppContext switch Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault to set MultiSubnetFailover=true by default in connection string.
    (#​3851)

Who Benefits:

  • Applications that need MultiSubnetFailover enabled globally without modifying connection strings.

Impact:

  • Applications can now enable MultiSubnetFailover globally using one of the following methods:
// In application code
AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault", true);
// In runtimeconfig.json
{
  "configProperties": {
    "Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault": true
  }
}
<!-- In App.Config -->
<runtime>
  <AppContextSwitchOverrides value="Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault=true" />
</runtime>

Changed

  • Optimized SqlStatistics execution timing by using Environment.TickCount instead of more expensive timing mechanisms.
    ... (truncated)

6.1.3

This update includes the following changes since the 6.1.2 release:

Added

App Context Switch for Ignoring Server-Provided Failover Partner

What Changed:

  • A new app context switch Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner was introduced to let the client ignore server-provided failover partner info in Basic Availability Groups (BAGs). When the switch is enabled, only the failover partner specified in the connection string is used; server-supplied partner values are skipped. This context switch was introduced in PR #​3702.

Who Benefits:

  • Applications connecting to SQL Server BAGs using TCP and custom ports, especially where the server's provided partner name lacks the protocol, host, or port. This avoids connection failures when the server-provided partner is incompatible or incomplete.
  • Teams who manage availability groups and rely on client-side control of failover behavior in heterogeneous networking environments.

Impact:

  • If your environment might be affected (i.e., you operate a BAG with custom ports, or have experienced failures after failover), you can enable the new switch in your application:
AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner", true);
  • Then, ensure your connection string includes your preferred failover partner (with correct tcp:host,port) so that the client uses that instead of the server's suggestion.
  • Without enabling this, by default, the client continues to prefer the server-provided partner, maintaining backwards compatibility.

Fixed

  • Fixed an issue to ensure reliable metrics initialization during startup, preventing missed telemetry when EventSource is enabled early. (#​3718)

Target Platform Support

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

Dependencies

.NET Framework 4.6.2+

  • Azure.Core 1.47.1
  • Azure.Identity 1.14.2
  • Microsoft.Bcl.Cryptography 8.0.0
  • Microsoft.Data.SqlClient.SNI 6.0.2
  • Microsoft.Extensions.Caching.Memory 8.0.1
  • Microsoft.IdentityModel.JsonWebTokens 7.7.1
  • Microsoft.IdentityModel.Protocols.OpenIdConnect 7.7.1
  • System.Buffers 4.5.1
  • System.Data.Common 4.3.0
  • System.Security.Cryptography.Pkcs 8.0.1
  • System.Text.Encodings.Web 8.0.0
    ... (truncated)

6.1.2

This update brings the below changes over the previous stable release:

Fixed

  • Fixed an issue where initializing PerformanceCounters would throw System.InvalidOperationException #​3629
  • Fixed an issue where a Custom SqlClientAuthenticationProvider was being overwritten by default implementation. #​3651
  • Fixed a concurrency issue in connection pooling where the number of active connections could be lower than the configured maximum pool size. #​3653

Commits viewable in compare view.

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

Release notes

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

18.12.0

Security fix

This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: microsoft/vstest#16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See microsoft/vstest#16652

What's Changed

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

18.11.1

Security fix

This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.11.0.
Fixed in: Microsoft.TestPlatform.CLI 18.11.1.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: microsoft/vstest#16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See microsoft/vstest#16652

What's Changed

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

Commits viewable in compare view.

Updated Scalar.AspNetCore from 2.19.0 to 2.21.0.

Release notes

Sourced from Scalar.AspNetCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated System.Security.Cryptography.Pkcs from 10.0.13 to 10.0.15.

Release notes

Sourced from System.Security.Cryptography.Pkcs's releases.

No release notes found for this version range.

Commits viewable in compare view.

Pinned WolverineFx.Http at 6.64.2.

Release notes

Sourced from WolverineFx.Http's releases.

6.64.2

Wolverine 6.64.2 is a patch release on the 6.x maintenance line (the 6.0 branch). It backports two Wolverine.HTTP fixes from 7.0 and adds no public API.

Fixes

  • #​5562: [DeduplicatedWithResponse] now works with multipart uploads and form posts. A retried upload or form post gets the first response again, where it used to get a 422. An endpoint that binds a form value is no longer refused. A form that ASP.NET Core reads before the endpoint (an antiforgery token sent as a form field) is fingerprinted too, and the antiforgery token is left out of the fingerprint, because a browser that reloads the page gets a new token for the same request. Thanks to @​esond (#​5563).
  • #​5463: Wolverine.HTTP reads form data asynchronously, so a request no longer blocks a thread on a synchronous Request.Form read. #​5562 builds on this. Thanks to @​uniquelau.

Known 6.x behavior, unchanged: with UseAntiforgery(), a form post with no token answers 500 rather than 400, because ASP.NET Core throws when the endpoint reads a form that failed antiforgery validation. 7.0 answers 400 through its in-endpoint antiforgery check (GH-5147), which is not backported.

Full change list: #​5575.

6.64.1

Wolverine 6.64.1 is a patch release on the 6.x maintenance line (the 6.0 branch). It backports four bug fixes from 7.0 and adds no public API.

Fixes

  • #​5456: the codegen-preview, describe-routing and describe commands no longer fail on an application that has a recurring schedule.
  • #​5458: in Solo mode on Polecat / SQL Server, a paused event-subscription agent now stops and stays stopped, instead of advancing although its pause is persisted.
  • #​5533: on native-ack listeners, the in-memory idempotency guard no longer acknowledges a redelivery that is still in flight. An in-flight duplicate is held unsettled, and only one that has already been processed is acknowledged.
  • #​5547: with inline retries, a failed attempt's tracing span now ends before the next attempt runs, instead of staying open across the retry and the dead-letter move.
  • #​5498 (already on 6.0 through #​5566): MySQL node-record housekeeping no longer deadlocks.

Build and CI

  • CI now runs on the 6.0 branch, so 6.x releases are gated like main.
  • The Native AOT smoke projects no longer pin Microsoft.DotNet.ILCompiler. The pin conflicted with the .NET 11 SDK's runtime pack (a backport of the fix on main).
  • The Aspire sample AppHosts moved to Aspire 13.6.5 for GHSA-f7vh-h5g3-7jrh. This affects the samples only, not any published package.

Not included: #​5562 ([DeduplicatedWithResponse] with multipart and form bodies). It depends on 7.0's async form-read rework.

Full change list: #​5571.

6.64.0

A small release: three fixes, one of them a new observer signal, and a JasperFx and Weasel bump. JasperFx moves from 2.100.1 to 2.102.0 and Weasel from 9.49.0 to 9.50.0; Marten (9.58.0), Polecat (5.49.0) and Fisher (1.28.0) are unchanged. There is no schema change and no breaking API change.

Fixes

  • Native-ack listeners: on a group-partitioned NativeAck endpoint, an envelope settled before it reached a handler (an unknown message type, an unreadable payload) is released from the lease tracker and the in-memory idempotency guard. It used to stay tracked until the lease ceiling and then log a false "unsettled for 00:59:xx" warning, an hour after it was completed (GH-5443).
  • Circuit breakers: IWolverineObserver.CircuitBreakerReset is now raised, once per trip, when a listener the breaker paused accepts messages again. Nothing ever raised it before, so an alert opened on CircuitBreakerTripped could never be closed by Wolverine's own signal. A new overload, CircuitBreakerReset(Endpoint, CircuitBreakerResetReason), says whether the listener came back on its own after PauseTime or through an explicit start or restart. Its default forwards to the existing one-argument member, so existing observers keep working unchanged (GH-5446).
  • Rabbit MQ: ResetResourceState() no longer adds a new wolverine.response.* queue on every call. Each reset had been declaring and purging every reply queue built so far, so a test suite that resets before each test slowed down with every test, and a sender started after a reset could send its replies to a queue nobody listened to, so InvokeAsync<T>() timed out (GH-5452, thanks to @​alesdvorakcz).

Docs

  • The command line runs from a Native AOT binary since JasperFx 2.101.0 (#​5442).
  • The resource setup hosted service migrates message storage regardless of AutoCreate (#​5445).

What's Changed

Full Changelog: JasperFx/wolverine@V6.63.0...V6.64.0

Commits viewable in compare view.

Pinned WolverineFx.Marten at 6.64.2.

Release notes

Sourced from WolverineFx.Marten's releases.

6.64.2

Wolverine 6.64.2 is a patch release on the 6.x maintenance line (the 6.0 branch). It backports two Wolverine.HTTP fixes from 7.0 and adds no public API.

Fixes

  • #​5562: [DeduplicatedWithResponse] now works with multipart uploads and form posts. A retried upload or form post gets the first response again, where it used to get a 422. An endpoint that binds a form value is no longer refused. A form that ASP.NET Core reads before the endpoint (an antiforgery token sent as a form field) is fingerprinted too, and the antiforgery token is left out of the fingerprint, because a browser that reloads the page gets a new token for the same request. Thanks to @​esond (#​5563).
  • #​5463: Wolverine.HTTP reads form data asynchronously, so a request no longer blocks a thread on a synchronous Request.Form read. #​5562 builds on this. Thanks to @​uniquelau.

Known 6.x behavior, unchanged: with UseAntiforgery(), a form post with no token answers 500 rather than 400, because ASP.NET Core throws when the endpoint reads a form that failed antiforgery validation. 7.0 answers 400 through its in-endpoint antiforgery check (GH-5147), which is not backported.

Full change list: #​5575.

6.64.1

Wolverine 6.64.1 is a patch release on the 6.x maintenance line (the 6.0 branch). It backports four bug fixes from 7.0 and adds no public API.

Fixes

  • #​5456: the codegen-preview, describe-routing and describe commands no longer fail on an application that has a recurring schedule.
  • #​5458: in Solo mode on Polecat / SQL Server, a paused event-subscription agent now stops and stays stopped, instead of advancing although its pause is persisted.
  • #​5533: on native-ack listeners, the in-memory idempotency guard no longer acknowledges a redelivery that is still in flight. An in-flight duplicate is held unsettled, and only one that has already been processed is acknowledged.
  • #​5547: with inline retries, a failed attempt's tracing span now ends before the next attempt runs, instead of staying open across the retry and the dead-letter move.
  • #​5498 (already on 6.0 through #​5566): MySQL node-record housekeeping no longer deadlocks.

Build and CI

  • CI now runs on the 6.0 branch, so 6.x releases are gated like main.
  • The Native AOT smoke projects no longer pin Microsoft.DotNet.ILCompiler. The pin conflicted with the .NET 11 SDK's runtime pack (a backport of the fix on main).
  • The Aspire sample AppHosts moved to Aspire 13.6.5 for GHSA-f7vh-h5g3-7jrh. This affects the samples only, not any published package.

Not included: #​5562 ([DeduplicatedWithResponse] with multipart and form bodies). It depends on 7.0's async form-read rework.

Full change list: #​5571.

6.64.0

A small release: three fixes, one of them a new observer signal, and a JasperFx and Weasel bump. JasperFx moves from 2.100.1 to 2.102.0 and Weasel from 9.49.0 to 9.50.0; Marten (9.58.0), Polecat (5.49.0) and Fisher (1.28.0) are unchanged. There is no schema change and no breaking API change.

Fixes

  • Native-ack listeners: on a group-partitioned NativeAck endpoint, an envelope settled before it reached a handler (an unknown message type, an unreadable payload) is released from the lease tracker and the in-memory idempotency guard. It used to stay tracked until the lease ceiling and then log a false "unsettled for 00:59:xx" warning, an hour after it was completed (GH-5443).
  • Circuit breakers: IWolverineObserver.CircuitBreakerReset is now raised, once per trip, when a listener the breaker paused accepts messages again. Nothing ever raised it before, so an alert opened on CircuitBreakerTripped could never be closed by Wolverine's own signal. A new overload, CircuitBreakerReset(Endpoint, CircuitBreakerResetReason), says whether the listener came back on its own after PauseTime or through an explicit start or restart. Its default forwards to the existing one-argument member, so existing observers keep working unchanged (GH-5446).
  • Rabbit MQ: ResetResourceState() no longer adds a new wolverine.response.* queue on every call. Each reset had been declaring and purging every reply queue built so far, so a test suite that resets before each test slowed down with every test, and a sender started after a reset could send its replies to a queue nobody listened to, so InvokeAsync<T>() timed out (GH-5452, thanks to @​alesdvorakcz).

Docs

  • The command line runs from a Native AOT binary since JasperFx 2.101.0 (#​5442).
  • The resource setup hosted service migrates message storage regardless of AutoCreate (#​5445).

What's Changed

Full Changelog: JasperFx/wolverine@V6.63.0...V6.64.0

Commits viewable in compare view.

Updated WolverineFx.RuntimeCompilation from 6.63.0 to 6.64.2.

Release notes

Sourced from WolverineFx.RuntimeCompilation's releases.

6.64.2

Wolverine 6.64.2 is a patch release on the 6.x maintenance line (the 6.0 branch). It backports two Wolverine.HTTP fixes from 7.0 and adds no public API.

Fixes

  • #​5562: [DeduplicatedWithResponse] now works with multipart uploads and form posts. A retried upload or form post gets the first response again, where it used to get a 422. An endpoint that binds a form value is no longer refused. A form that ASP.NET Core reads before the endpoint (an antiforgery token sent as a form field) is fingerprinted too, and the antiforgery token is left out of the fingerprint, because a browser that reloads the page gets a new token for the same request. Thanks to @​esond (#​5563).
  • #​5463: Wolverine.HTTP reads form data asynchronously, so a request no longer blocks a thread on a synchronous Request.Form read. #​5562 builds on this. Thanks to @​uniquelau.

Known 6.x behavior, unchanged: with UseAntiforgery(), a form post with no token answers 500 rather than 400, because ASP.NET Core throws when the endpoint reads a form that failed antiforgery validation. 7.0 answers 400 through its in-endpoint antiforgery check (GH-5147), which is not backported.

Full change list: #​5575.

6.64.1

Wolverine 6.64.1 is a patch release on the 6.x maintenance line (the 6.0 branch). It b...

Description has been truncated

Bumps AWSSDK.S3 from 4.0.104.11 to 4.1.1
Bumps coverlet.collector from 10.1.0 to 10.1.1
Bumps Fido2 from 4.3.2 to 4.3.3
Bumps JasperFx.Events from 2.101.0 to 2.102.0
Bumps JasperFx.Events.SourceGenerator from 2.101.0 to 2.102.0
Bumps Marten from 9.58.0 to 9.62.0
Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.14 to 10.0.15
Bumps Microsoft.AspNetCore.OpenApi from 10.0.14 to 10.0.15
Bumps Microsoft.Data.SqlClient from 6.1.1 to 6.1.8
Bumps Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0
Bumps Scalar.AspNetCore from 2.19.0 to 2.21.0
Bumps System.Security.Cryptography.Pkcs from 10.0.13 to 10.0.15
Bumps WolverineFx.Http from 6.63.0 to 6.64.2
Bumps WolverineFx.Marten from 6.63.0 to 6.64.2
Bumps WolverineFx.RuntimeCompilation from 6.63.0 to 6.64.2

---
updated-dependencies:
- dependency-name: AWSSDK.S3
  dependency-version: 4.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: coverlet.collector
  dependency-version: 10.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-menores
- dependency-name: Fido2
  dependency-version: 4.3.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-menores
- dependency-name: JasperFx.Events
  dependency-version: 2.102.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: JasperFx.Events.SourceGenerator
  dependency-version: 2.102.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: Marten
  dependency-version: 9.62.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-menores
- dependency-name: Microsoft.AspNetCore.OpenApi
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-menores
- dependency-name: Microsoft.Data.SqlClient
  dependency-version: 6.1.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-menores
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: Scalar.AspNetCore
  dependency-version: 2.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: System.Security.Cryptography.Pkcs
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-menores
- dependency-name: System.Security.Cryptography.Pkcs
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-menores
- dependency-name: WolverineFx.Http
  dependency-version: 6.64.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: WolverineFx.Marten
  dependency-version: 6.64.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: WolverineFx.RuntimeCompilation
  dependency-version: 6.64.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #84.

@dependabot dependabot Bot closed this Nov 19, 2026
@dependabot
dependabot Bot deleted the dependabot/nuget/nuget-menores-bdb25c7f7b branch November 19, 2026 07:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants