Skip to content
This repository was archived by the owner on Oct 26, 2026. It is now read-only.

Bump the nuget-minor-patch group with 7 updates - #11

Merged
github-actions[bot] merged 1 commit into
mainfrom
dependabot/nuget/Week-01---API/Auction/AuctionApi/nuget-minor-patch-fcd557d865
Oct 26, 2026
Merged

Bump the nuget-minor-patch group with 7 updates#11
github-actions[bot] merged 1 commit into
mainfrom
dependabot/nuget/Week-01---API/Auction/AuctionApi/nuget-minor-patch-fcd557d865

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Updated Dapper from 2.1.79 to 2.1.89.

Release notes

Sourced from Dapper's releases.

2.1.89

What's Changed

New Contributors

Full Changelog: DapperLib/Dapper@2.1.86...2.1.89

2.1.86

What's Changed

Full Changelog: DapperLib/Dapper@2.1.79...2.1.86

Commits viewable in compare view.

Updated Microsoft.Data.SqlClient from 7.0.2 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)

7.1.0

This is the general availability release of Microsoft.Data.SqlClient 7.1. It closes out the 7.1 preview cycle with application identity reporting for telemetry, the deprecation of TransparentNetworkIPResolution, and a set of connection, transaction, and Named Pipes fixes.

Important — package version alignment: Starting with the 7.0.2 release, the Microsoft.Data.SqlClient driver and its companion packages share a single aligned version. The 7.1.0 GA release continues this alignment; the following packages ship together as 7.1.0:

  • 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 continues to version independently and remains at 1.0.0.)

Applications must reference the same versions of Microsoft.Data.SqlClient and its extensions for best compatibility. In particular, applications that reference Microsoft.Data.SqlClient.Extensions.Azure must upgrade it to 7.1.0 when upgrading Microsoft.Data.SqlClient to 7.1.0.

Compatibility guarantee: All aligned assemblies ship with FileVersion 7.1.0.x and AssemblyVersion 7.0.0.0. The AssemblyVersion is unchanged from 7.0.2, so upgrading from 7.0.2, 7.0.3, or any 7.1 preview to 7.1.0 does not require any new .NET Framework strong-name binding redirects. Applications upgrading from 7.0.0 or 7.0.1 should note that Extensions.Azure, Extensions.Abstractions, and Internal.Logging raised their AssemblyVersion from 1.0.0.0 to 7.0.0.0 in 7.0.2; see those release notes for the one-time .NET Framework impact.

Companion package release notes

Changes Since 7.1.0-preview3

Added

Application Identity in the USERAGENT Payload

What Changed:

  • Added a RegisteredApplication enum and a matching SqlConnection.RegisteredApplication property that let a library or tool identify itself to SQL Server through version 2 of the TDS USERAGENT feature extension. The payload also carries a new driver-owned 64-bit Driver Properties flag field; bit 0 reports whether connection pool V2 is enabled for the process. Both fields are emitted as unpadded uppercase hexadecimal. (#​3201, #​4632)

Who Benefits:

  • Middleware and tooling built on top of the driver — Entity Framework Core, Semantic Kernel, SQL Server Management Studio, SqlPackage, Data API Builder, and similar — can be distinguished in server-side telemetry without the driver accepting arbitrary user-supplied user-agent text. This originated as a request from the Entity Framework Core team.
  • Service operators gain a more accurate picture of which client stacks are connecting, which helps when diagnosing workload-specific behavior.

Impact:

  • Purely additive from the application's perspective: a newly created physical connection whose RegisteredApplication is unset reports Unknown (0). On the wire the field itself is new — USERAGENT payload v1 carried no application identifier, while v2 always emits one.
  • Set the property before calling Open or OpenAsync. Assigning it while the connection is connecting or open throws InvalidOperationException.
using var connection = new SqlConnection(connectionString);
connection.RegisteredApplication = RegisteredApplication.EntityFrameworkCore;
await connection.OpenAsync();
  • The enum is ushort-backed and marked [CLSCompliant(false)]. Values are partitioned by range: 0x0001–0x7FFF for Microsoft-defined large-scale applications, 0x8000–0xBFFF for small-scale use, and 0xC000–0xFFFF for public/developer use. Applications that are not yet registered can cast an unassigned value from the appropriate range.
    ... (truncated)

7.1.0-preview3

This update brings the following changes since the 7.1.0-preview2 release.

Package version alignment: The Microsoft.Data.SqlClient driver and its companion packages continue the aligned versioning introduced in 7.0.2. All five packages listed below ship together as 7.1.0-preview3. (Microsoft.SqlServer.Server continues to version independently and remains at 1.0.0.) Applications that reference Microsoft.Data.SqlClient.Extensions.Azure must upgrade it to 7.1.0-preview3 when upgrading Microsoft.Data.SqlClient.

Compatibility guarantee: All aligned assemblies ship with FileVersion 7.1.0.x and AssemblyVersion 7.0.0.0 — unchanged from 7.0.2 — so upgrading from 7.0.2 to 7.1.0-preview3 does not require any new .NET Framework strong-name binding redirects.

Packages in this release

Microsoft.Data.SqlClient 7.1.0-preview3

Added

  • Asynchronous key store provider APIs for Always Encrypted — four virtual methods on SqlColumnEncryptionKeyStoreProvider with CancellationToken support. Purely additive; defaults delegate to the synchronous methods, so existing providers are unaffected (#​3672, #​3673)
  • Connection Pool V2 nears parity with the default pool (opt-in via Switch.Microsoft.Data.SqlClient.UseConnectionPoolV2):
    • Transaction support (#​4487)
    • Broken-connection replacement during command execution (#​4429)
    • Background warmup to Min Pool Size and automatic replenishment (#​4452)
    • Idle pruning driven by Connection Idle Timeout (#​4463)
    • Optional ConcurrencyLimiter rate limiting for new physical connections (#​4395, #​4396)
    • Leaked connection reclamation, including the previously always-zero number-of-reclaimed-connections counter (#​4529)
    • Metrics and tracing parity with the default pool (#​4504)

Changed

  • Single cross-platform build — Windows-only native SNI types now trim cleanly on Linux and macOS. Package structure and contents unchanged (#​4207, #​4239, #​4465, #​4474)
  • Async read-path allocations restored to baseline via PacketData node reuse — ExecuteReaderAsync goes from +120.9% to +0.1% against 6.1.6 (#​4536)
  • SqlBulkCopy skips graph alias mapping when no graph pseudo-columns are present, recovering a regression from #​3677 (#​4535)
  • No formatted trace string is allocated when SqlClientEventSource tracing is disabled, recovering a memory regression against 6.1.6. Trace output unchanged (#​4528)
  • net9.0 dependencies moved to 9.0.18; System.Threading.RateLimiting added to packaged metadata. Other targets keep their 8.0.x pins (#​4507)
  • Microsoft.Data.SqlClient.SNI and .SNI.runtime updated to 7.1.0-preview3.26226.3 (#​4564)

Fixed

  • Always Encrypted VSM/HGS attestation now verifies the enclave public key is bound to the signed report, using a fixed-time SHA-256 comparison against EnclaveData (#​4532)
  • SqlConnectionFactory no longer wakes the process every 30 seconds when no pools exist — including with Pooling=False and after ClearAllPools() (#​1881, #​4479)
  • Connection pool performance counters affecting the default pool as well as pool V2 — active-soft-connects and number-of-active-connections could go negative after a failed activation, and several gauges drifted upward permanently after a broken connection was replaced (#​4504)
  • OverflowException when sending large decimal values with explicit Precision and Scale, which primarily affected Always Encrypted (#​1655, #​4443)
  • TDS stream error when passing a DateOnly value with SqlDbType.Variant (net8.0/net9.0) (#​3953, #​4294)
  • DateOnly in table-valued parameter sql_variant columns sent as datetime instead of date, which overflowed for values valid as date (net8.0/net9.0) (#​3934, #​4439)
  • ServerCertificate keyword ignored when the platform reported no TLS policy errors. It is now always compared, and an unloadable certificate fails closed with SSLCertificateAuthenticationException instead of silently falling back to host-name validation (#​4445)
  • SqlConnection.AccessTokenCallback not disabling TNIR by default, plus pool-key construction and SspiContextProvider exclusivity with token auth (net462 for the TNIR behavior) (#​4520)
  • Fatal exceptions such as OutOfMemoryException captured into faulted Tasks across several SqlBulkCopy, SqlDataReader, and SqlCommand async entry points (#​4437)
  • Entra ID authentication failing against multi-segment authorities such as the Dataverse / Dynamics 365 TDS endpoint. Ships in Microsoft.Data.SqlClient.Extensions.Azure (#​4496, #​4521)

Full details: release-notes/7.1/7.1.0-preview3.md

Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider 7.1.0-preview3

Added

  • SqlColumnEncryptionAzureKeyVaultProvider overrides the four asynchronous key store provider methods introduced in #​3673, calling the Azure SDK's own async APIs and flowing the supplied CancellationToken (#​4540)
  • Concurrent cache misses for the same key collapse into a single Key Vault request. The gate is only awaited, so no thread blocks, and misses for different keys still proceed in parallel (#​4540)
    ... (truncated)

7.1.0-preview2

This update brings the following changes since the 7.1.0-preview1 release.

Package version alignment: The Microsoft.Data.SqlClient driver and its companion packages continue the aligned versioning introduced in 7.0.2. All five packages listed below ship together as 7.1.0-preview2. (Microsoft.SqlServer.Server continues to version independently and remains at 1.0.0.) Applications that reference Microsoft.Data.SqlClient.Extensions.Azure must upgrade it to 7.1.0-preview2 when upgrading Microsoft.Data.SqlClient.

Compatibility guarantee: All aligned assemblies ship with FileVersion 7.1.0.x and AssemblyVersion 7.0.0.0 — unchanged from 7.0.2 — so upgrading from 7.0.2 to 7.1.0-preview2 does not require any new .NET Framework strong-name binding redirects.

Packages in this release

Microsoft.Data.SqlClient 7.1.0-preview2

Added

  • SqlConnection.GetSchemaAsync overloads with CancellationToken support (#​3005)
  • SQL Graph pseudo-column aliases ($node_id, $edge_id, $from_id, $to_id) accepted in SqlBulkCopy mappings (#​3677)
  • SqlBatchCommand.CommandBehavior and SqlBatch.ExecuteReader(CommandBehavior) are now honored (#​4125)
  • Configurable idle connection timeout via Connection Idle Timeout / SqlConnectionStringBuilder.IdleTimeout (opt-in via Switch.Microsoft.Data.SqlClient.UseLegacyIdleTimeoutBehavior=false) (#​4295)

Changed

  • Connect Timeout now propagates through the pool when Switch.Microsoft.Data.SqlClient.UseOverallConnectTimeoutForPoolWait=true is set (default off; introduces a Microsoft.Bcl.TimeProvider dependency) (#​4270)
  • SQL Server 2025 json type added to the DataTypes collection returned by SqlConnection.GetSchema (#​3858)
  • Internal state-machine hardening via Interlocked.CompareExchange guards (#​4267)
  • Internal cleanup of connection-options inheritance and related pool interfaces (#​4237, #​4261, #​4235, #​4415, #​4334)
  • LCID hardcoded mappings to avoid repeated culture lookups (#​4212)
  • Allocation reductions on SqlErrorCollection and null-return paths (#​4157, #​4099, #​4102)
  • Improved EnclaveDiffieHellmanInfo.Size accuracy (#​4346)
  • SqlVector<float> serialization is now explicitly little-endian for cross-architecture consistency (#​3861)
  • Bundled .NET 10 SDK updated to 10.0.300 (#​4287)

Fixed

  • NullReferenceException in SqlCommand.Cancel() when the connection has already been torn down (#​4372)
  • Always Encrypted CMK signature verification incorrectly reusing cached results after a prior failure (#​4339)
  • Missing TDS token / feature-ack length bounds checks (spoofing server could trigger unbounded allocations) (#​4340)
  • SqlBulkCopy failing in least-privilege environments (#​4306)
  • Always Encrypted CekMdVersion / EkValueCount reads aligned with the TDS specification (#​4240)
  • LoginWithFailover parser-state validation (#​4140)
  • SPN during login now uses the resolved port instead of instance name for Protocol=None / Protocol=Admin (#​4180)
  • Race in SqlConnection.TryOpenInner that could surface as InvalidCastException now returns a deterministic InvalidOperationException (#​4179)
  • Multiple CancellationTokenSource leaks in SqlDataReader, SqlConnection, SqlCommand reconnect paths, and sequential-stream helpers (#​4009)
  • Docs fix for server certificate configuration (#​4408)

Removed (breaking)

  • SQL Server 7.0 / 2000 code paths removed; Type System Version=SQL Server 2000 now throws ArgumentException at open. Applications should switch to Latest (or another supported value). No change to server-version support — 7.0 / 2000 were already rejected during login version negotiation. (#​4015)

Full details: release-notes/7.1/7.1.0-preview2.md

Microsoft.Data.SqlClient.Extensions.Azure 7.1.0-preview2

Added — WAM (Windows Account Manager) broker support for Entra ID authentication (Windows only) (#​4288, #​4388)

  • Covers ActiveDirectoryIntegrated, ActiveDirectoryInteractive, ActiveDirectoryDeviceCodeFlow, and the deprecated ActiveDirectoryPassword modes.
    ... (truncated)

7.1.0-preview1

This update brings the following changes since the 7.0.0 release:

Added

SqlBatch Support on .NET Framework

What Changed:

  • Added SqlBatch and related batch-command support for the .NET Framework target so the batching API is now available across the full supported platform matrix, including net462. (#​3926)

Who Benefits:

  • Applications that target .NET Framework but also want to use the newer batching APIs no longer need a separate implementation strategy from .NET 8/9 applications.
  • Libraries that multi-target .NET Framework and modern .NET can use a more consistent data-access surface area.

Impact:

  • SqlBatch, SqlBatchCommand, and the related execution methods are now usable on .NET Framework builds in addition to .NET.

Cross-Driver Connection-String Synonym Alignment

What Changed:

  • Added additional accepted connection-string synonyms for better compatibility with other SQL Server drivers and existing connection-string conventions. Newly accepted synonyms include ColumnEncryption, ConnectTimeout, FailoverPartner, PacketSize, and WorkstationId. (#​4192)

Who Benefits:

  • Applications migrating connection strings from other SQL Server drivers or shared infrastructure can reuse more existing keywords without rewriting them first.

Impact:

  • Existing canonical keywords continue to work unchanged; this preview simply accepts more equivalent aliases during parsing.

Changed

Type Forwards for Authentication Abstractions

What Changed:

  • Added type forwards from the core Microsoft.Data.SqlClient assembly to public authentication-related types that were moved into Microsoft.Data.SqlClient.Extensions.Abstractions, including SqlAuthenticationMethod, SqlAuthenticationParameters, SqlAuthenticationProvider, SqlAuthenticationProviderException, and SqlAuthenticationToken. (#​4067, #​4117)

Who Benefits:

  • Applications and libraries compiled against earlier package layouts retain binary compatibility when those authentication types are resolved from the core assembly name.

Impact:

  • No application code changes are required; the type forwards preserve existing compiled references.

User Agent Feature Extension Enabled by Default

... (truncated)

7.0.3

This update brings the following changes since the 7.0.2 release:

The core driver and its companion packages ship together as version 7.0.3. Update the companion packages you use alongside the driver to 7.0.3. Assembly versions remain 7.0.0.0, unchanged from 7.0.2.

Companion package release notes

Changed

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

Fixed

  • Fixed a SqlBulkCopy regression in environments where the application login cannot read sys.all_columns. Bulk copy now falls back to the earlier column-discovery behavior when that permission is unavailable. Support for hidden columns and SQL Graph column aliases still requires access to the metadata view.
    (#​4370, #​4306, #​4402)

  • Fixed a memory-allocation regression in connection and command operations caused by formatting diagnostic strings even when tracing was disabled. Also corrected trace messages that reported an incorrect object ID or could throw FormatException when traced values contained braces.
    (#​4528, #​4533)

  • 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, #​4583)

  • 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, #​4553)

  • 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, #​4561)

  • Fixed authentication state handling so clearing SqlConnection.AccessToken, AccessTokenCallback, or SspiContextProvider preserves the other authentication values in the connection pool key. Cloning a connection or updating its credential also preserves its SspiContextProvider. Combining a non-null SspiContextProvider with AccessToken or AccessTokenCallback now throws InvalidOperationException instead of silently discarding authentication state; applications must use one authentication mechanism at a time.
    (#​4520, #​4561, #​4644)

  • 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, #​4663)

Contributors

We thank the following public contributors. Their efforts toward this project are very much appreciated.

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)

... (truncated)

Commits viewable in compare view.

Updated Moq from 4.20.72 to 4.21.0.

Release notes

Sourced from Moq's releases.

4.21.0

What's Changed

✨ Implemented enhancements

🐛 Fixed bugs

🔨 Other

New Contributors

Full Changelog: devlooped/moq@v4.20.72...v4.21.0

Sponsors

The following sponsors made this release possible: @​clarius, @​MFB-Technologies-Inc, @​sandrock, @​drivenet, @​Keflon, @​tbolon, @​rbnswartz, @​jfoshee, @​Mrxx99, @​eajhnsn1, @​Jonathan-Hickey, @​KenBonny, @​SimonCropp, @​agileworks-eu, @​arsdragonfly, @​vezel-dev, @​ChilliCream, @​4OTC, @​DominicSchell, @​adalon, @​torutek, @​mccaffers, @​SeikaLogiciel, @​wizardness, @​eska-gmbh, @​geodata-no.

Thanks 💜

Commits viewable in compare view.

Updated NUnit from 4.3.2 to 4.6.1.

Release notes

Sourced from NUnit's releases.

4.6.1

See release notes for details.

4.6.0

See release notes for details.

4.5.1

See release notes for details.

4.5.0

See release notes for details.

4.4.0

See release notes for details.

Commits viewable in compare view.

Updated NUnit.Analyzers from 4.7.0 to 4.15.0.

Release notes

Sourced from NUnit.Analyzers's releases.

4.15.0

NUnit Analyzers 4.15 - September 12, 2026

This release of the NUnit Analyzers adds support for the new numeric types that will
be supported in NUnit 5. The release also improves NUnit1027 by inspecting base fixtures,
and NUnit1028 by supporting IAsyncDisposable.DisposeAsync in addition to the
existing IDisposable.Dispose. The release also includes bug fixes and dependency updates.

The release contains contributions from the following users (in alphabetical order):

  • @​jhavlicek-profinit
  • @​killergege
  • @​manfred-brands
  • @​mikkelbu
  • @​ngbrown
  • @​ramonsmits
  • @​stevenaw
  • @​uladz-zubrycki

Issues Resolved

Features and Enhancements

  • #​1019 NUnit1027 does not see [CancelAfter] inherited from a base fixture
  • #​1017 NU2047 reports failure for new numeric types
  • #​1001 NUnit1028: Allow DisposeAsync as an exception
  • #​999 [TestCaseSource] CA1812 suppression

Bugs

  • #​1013 Use of records crash the NonNullableFieldOrPropertyIsUninitializedSuppressor analyzer
  • #​998 Assert.EnterMultipleScope clears nullability suppress info

Tooling, Process, and Documentation

  • #​1005 Bump Microsoft.NET.Test.Sdk from 18.6.0 to 18.7.0
  • #​996 Bump Microsoft.NET.Test.Sdk from 17.14.1 to 18.6.0
  • #​993 chore: bump version

4.14.0

NUnit Analyzers 4.14 - June 1, 2026

This release of the NUnit Analyzers adds a new analyzer and associated codefix - NUnit2059 - that helps ensure that
async assertion methods in NUnit version 5 and higher - i.e. Assert.ThrowsAsync, Assert.CatchAsync, and
Assert.DoesNotThrowAsync - have their results observed, as these methods are awaitable from NUnit version 5.

The release contains contributions from the following users (in alphabetical order):

  • @​manfred-brands
  • @​mikkelbu

Issues Resolved

Features and Enhancements

  • #​988 Recognize that Assert.ThrowsAsync etc now return a Task that needs awaiting.

Tooling, Process, and Documentation

  • #​990 Bump cake.tool from 6.1.0 to 6.2.0
  • #​987 chore: bump version and correct errors in CHANGES.md

4.13.0

NUnit Analyzers 4.13 - May 2, 2026

This release of the NUnit Analyzers updates analyzer handling for the NUnit 4.6 API change that replaces
ActualValueDelegate<> with Func<> - see nunit/nunit#4824 for more information.
Analyzers now also consider the return type of Func<> in assertions. The release also includes one bug fix and
some dependency updates.

The release contains contributions from the following users (in alphabetical order):

  • @​manfred-brands
  • @​mikkelbu
  • @​RenderMichael

Issues Resolved

Features and Enhancements

  • #​982 Recognized Func<T> return values

Bugs

  • #​968 Whitespace issue in Does.Contain fixer when assert spans multiple lines

Tooling, Process, and Documentation

  • #​985 chore: Bump year to 2026 in copyrights
  • #​978 Bump cake.tool from 6.0.0 to 6.1.0
  • #​976 chore: Correct documentation
  • #​975 chore: bump version
  • #​956 Bump cake.tool from 4.0.0 to 6.0.0

4.12.0

NUnit Analyzers 4.12 - March 3, 2026

This release of the NUnit Analyzers improves NUnit1029 to account for TestCaseSource
support for params and optional arguments. It also introduces a new analyzer for incorrect
usage of Is.Not.Null.Or.Empty, fixes regressions in NUnit2005 and NUnit2055, and updates
NUnit package dependencies.

The release contains contributions from the following users (in alphabetical order):

  • @​Dreamescaper
  • @​manfred-brands
  • @​mikkelbu
  • @​nowsprinting
  • @​philipp-naused
  • @​stevenaw

Issues Resolved

Features and Enhancements

  • #​957 Relax NUnit1029 for TestCaseSource where method accepts a single "params" array
  • #​189 Warning when Is.Not.Null.Or.Empty used

Bugs

  • #​953 Code fix for NUnit2055 can generate invalid code for classic asserts
  • #​952 Code fix for NUnit2005 tries to use Is.Empty constraint on incompatible types.

Tooling, Process, and Documentation

  • #​973 chore: Bump NUnit version
  • #​970 chore: Bump NUnit to version 4.5.0
  • #​967 Fix note about works with Unity Test Framework
  • #​937 chore: bump version

4.11.2

NUnit Analyzers 4.11.2 - November 2, 2025

This release of the NUnit Analyzers fixes a problem in the NUnit2057 analyzer for unnecessary use of lambda
expressions. The release also extends NUnit2021 so that it can determining if Is.NaN or Is.Not.NaN constraints
are used on incompatible types.

The release contains contributions from the following users (in alphabetical order):

  • @​MaceWindu
  • @​manfred-brands
  • @​stevenaw

Issues Resolved

Features and Enhancements

  • #​929 Alert when using Is.NaN or Is.Not.NaN on an incompatible type

Bugs

  • #​945 [NUnit2057] Reported for Throws assert

4.11.1

NUnit Analyzers 4.11.1 - October 30, 2025

This release of the NUnit Analyzers fixes a regression related to the analysis of nullable enum parameters in
NUnit1001 and NUnit1031. The release also contains a new analyzer and codefix for unnecessary usage of lambda
expressions in asserts.

The release contains contributions from the following users (in alphabetical order):

  • @​MaceWindu
  • @​maksim-sovkov
  • @​manfred-brands

Issues Resolved

Features and Enhancements

  • #​927 Add new rule for unnecessary use of lambda expressions

Bugs

  • #​939 NUnit1001 - false positive for arguments with nullable enum parameters
  • #​938 [NUnit1031] False positive for nullable structs

4.11.0

NUnit Analyzers 4.11 - October 28, 2025

This release of the NUnit Analyzers includes improvements and fixes related to IDisposable handling and initialization
in SetUp and OneTimeSetUp methods. It also introduces the ability to configure additional methods that should be
treated as SetUp and TearDown methods by the analyzers. This can be done in the .editorconfig, and there are four
configurations for this:

  • dotnet_diagnostic.NUnit.additional_setup_methods
  • dotnet_diagnostic.NUnit.additional_teardown_methods
  • dotnet_diagnostic.NUnit.additional_one_time_setup_methods
  • dotnet_diagnostic.NUnit.additional_one_time_teardown_methods

Each configuration accepts a list of method names, separated by commas, semicolons, or spaces. For example:

dotnet_diagnostic.NUnit.additional_setup_methods = CustomSetup, MyInit

As in recent releases, a major part of this work was contributed by @​manfred-brands.

The release contains contributions from the following users (in alphabetical order):

  • @​AlisonAMorrison
  • @​BodrickLight
  • @​cbersch
  • @​manfred-brands
  • @​mikkelbu
  • @​PiotrKlecha
  • @​sbe-schleupen

Issues Resolved

Features and Enhancements

  • #​921 NUnit1032 - disposals in overridden methods not detected
  • #​919 NUnit1032/NUnit3002 - local functions not analyzed
  • #​918 NUnit2045 - false positive for inline usings
  • #​911 NUnit3002 doesn't recognize the using statement.
  • #​910 using declarations not recognized by NUnit2045

Bugs

  • #​922 NUnit1001 - false positive for arguments with generic parameters
  • #​914 Wrong position of NUnit1001 diagnostic for TestCase with four parameters or more

Tooling, Process, and Documentation

  • #​926 chore: Bump NUnit3TestAdapter
  • #​908 chore: bump version
  • #​885 Bump to NUnit version 4.4 when this is released

4.10.0

NUnit Analyzers 4.10 - August 9, 2025

This release of the NUnit Analyzers contains some minor improvements to NUnit2050, NUnit2056, and NUnit2007 as well
as some improvements to existing tests. Once again, @​manfred-brands was responsible for the majority of the work.

The release contains contributions from the following users (in alphabetical order):

  • @​dfev77
  • @​manfred-brands
  • @​mikebro
  • @​mikkelbu

Issues Resolved

Bugs

  • #​901 False positive on NUnit2050
  • #​899 NUnit2056 analyzer's code fix removes comments and empty lines above it.
  • #​896 NUnit2007 shouldn't trigger for generic types e.g. typeof(T)

Tooling, Process, and Documentation

  • #​905 NUnit4.4 alpha -> beta changes
  • #​897 chore: Correct typo in NUnit2045.md
  • #​894 Improve tests by adding ↓ to tests were it is missing in the source
  • #​887 chore: bump version

4.9.2

NUnit Analyzers 4.9.2 - June 17, 2025

This release of the NUnit Analyzers extends the NUnit3001 nullability suppressor
to also work in the context of Assert.EnterMultipleScope and other using statements.

The release contains contributions from the following users (in alphabetical order):

  • @​artificialWave
  • @​manfred-brands
  • @​mikkelbu

Issues Resolved

Features and Enhancements

  • #​892 Assert.EnterMultipleScope not detecting nullability properly

4.9.1

NUnit Analyzers 4.9.1 - June 12, 2025

This release of the NUnit Analyzers fixes a problem with the code-fix for translating
Assert.Multiple/Assert.MultipleAsync into the new Assert.EnterMultipleScope format
when the test method already is asynchronous and have a return type different from Task.

The release contains contributions from the following users (in alphabetical order):

  • @​MaceWindu
  • @​manfred-brands
  • @​mikkelbu

Issues Resolved

Bugs

  • #​888 Assert.MultipleAsync -> EnterMultipleScope autofix produce invalid code

4.9.0

NUnit Analyzers 4.9 - June 11, 2025

This release of the NUnit Analyzers adds several new analyzers. For the RangeAttribute,
the analyzers now warn about potential issues at runtime.

It also introduces an analyzer and code fix for translating
Assert.Multiple/Assert.MultipleAsync into the new Assert.EnterMultipleScope format, as well
as for converting is T checks into Is.InstanceOf<T>() constraints.

For NUnit2021, the analyzer now respects UsingPropertiesComparer, including enhancements
that will be available in NUnit 4.4.

Finally, this release includes improvements to NUnit2007, NUnit2045, and NUnit4002.
See the list of resolved issues below for more details.

The release contains contributions from the following users (in alphabetical order):

  • @​MaceWindu
  • @​manfred-brands
  • @​mikkelbu
  • @​OsirisTerje
  • @​stevenaw

Issues Resolved

Features and Enhancements

  • #​880 NUnit2007 could flag typeof() as a constant first parameter
  • #​866 When Assert.Multiple is found, should suggest to convert to Assert.EnterMultipleScope
  • #​865 NUnit 2045 suggest Assert.Multiple, but should suggest Assert.EnterMultipleScope
  • #​857 NUnit2021 Should not raise for UsingPropertiesComparer
  • #​765 Add Rule for converting is T into Is.InstanceOf()
  • #​89 Test the correct usage of the Range attribute

Bugs

  • #​879 NUnit4002 shouldn't trigger for T vs nullable<T> struct types

Tooling, Process, and Documentation

  • #​868 chore: bump version

4.8.1

NUnit Analyzers 4.8.1 - May 29, 2025

This release of the NUnit Analyzers fixes a problem with NUnit4002 when applied to comparisons between non-number
types - e.g. strings.

The release contains contributions from the following users (in alphabetical order):

  • @​adrianbanks
  • @​manfred-brands
  • @​mikkelbu

Issues Resolved

Bugs

  • #​870 Compilation error caused by exception in an analyzer after updating to v4.8.0

4.8.0

NUnit Analyzers 4.8 - May 22, 2025

This release of the NUnit Analyzers adds a new diagnostic NUnit1034 that checks
whether base TestFixtures are declared as abstract. When a base class is not abstract
it will also be run as a standalone test which is most times not the intention.

The release also contains some fixes to NUnit4002 and Nunit2045.

The release contains contributions from the following users (in alphabetical order):

  • @​Bartleby2718
  • @​CharliePoole
  • @​MaceWindu
  • @​manfred-brands
  • @​mikkelbu
  • @​Rabadash8820

Issues Resolved

Features and Enhancements

  • #​840 Detect incorrect or questionable use of TestFixture inheritance.

Bugs

  • #​862 NUnit.Analyzers doesn't recognize the version of NUnit in use
  • #​856 NUnit4002 shouldn't trigger for unknown types

Tooling, Process, and Documentation

  • #​861 Add missing backticks in NUnit4002.md
  • #​855 chore: bump version

Commits viewable in compare view.

Updated NUnit3TestAdapter from 5.0.0 to 5.2.0.

Release notes

Sourced from NUnit3TestAdapter's releases.

5.2.0

See release notes

5.1.0

See release notes

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.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the nuget-minor-patch group with 7 updates
8ca674f 
Bumps Dapper from 2.1.79 to 2.1.89
Bumps Microsoft.Data.SqlClient from 7.0.2 to 7.1.1
Bumps Moq from 4.20.72 to 4.21.0
Bumps NUnit from 4.3.2 to 4.6.1
Bumps NUnit.Analyzers from 4.7.0 to 4.15.0
Bumps NUnit3TestAdapter from 5.0.0 to 5.2.0
Bumps Swashbuckle.AspNetCore from 10.2.3 to 10.3.1

---
updated-dependencies:
- dependency-name: Dapper
  dependency-version: 2.1.89
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-patch
- dependency-name: Dapper
  dependency-version: 2.1.89
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-patch
- dependency-name: Microsoft.Data.SqlClient
  dependency-version: 7.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: Microsoft.Data.SqlClient
  dependency-version: 7.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: Moq
  dependency-version: 4.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: NUnit
  dependency-version: 4.6.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: NUnit
  dependency-version: 4.6.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: NUnit.Analyzers
  dependency-version: 4.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: NUnit.Analyzers
  dependency-version: 4.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: NUnit3TestAdapter
  dependency-version: 5.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: NUnit3TestAdapter
  dependency-version: 5.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: Swashbuckle.AspNetCore
  dependency-version: 10.3.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Oct 26, 2026
@github-actions
github-actions Bot enabled auto-merge (squash) October 26, 2026 20:31
@github-actions
github-actions Bot merged commit 3c9135b into main Oct 26, 2026
10 checks passed
@dependabot
dependabot Bot deleted the dependabot/nuget/Week-01---API/Auction/AuctionApi/nuget-minor-patch-fcd557d865 branch October 26, 2026 20:33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

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

Development

Successfully merging this pull request may close these issues.

0 participants