[dependabot]

Updated Azure.Security.KeyVault.Secrets from 4.11.0 to 4.11.2.

Release notes

Sourced from Azure.Security.KeyVault.Secrets's releases.

4.11.2

4.11.2 (2026-10-02)

Bugs Fixed

• Fixed handling of claims challenges when the authentication challenge cache is empty or cleared while a request is in flight.
• Fixed an issue in the challenge-based authentication policy where a cached authentication challenge accepted with challenge resource verification disabled could be reused by a separate default-strict client without revalidating the challenge resource.
• Improved authentication challenge resource validation.

Commits viewable in compare view.

Updated coverlet.collector from 10.0.1 to 10.1.0.

Release notes

Sourced from coverlet.collector's releases.

10.1.0

Improvements

• Publish Microsoft.Testing.Platform coverage messages from coverlet.MTP #​2019
• Implement dynamic exclusion filters for assemblies (Coverlet.MTP) #​1946
• Replace legacy .sln files with modern .slnx format #​1966
• coverlet.console: add trace diagnostics and actionable warnings for instrumentation/hit/empty-result failures #​2005
• Relax auto-property skip logic and improve coverage for records #​1941

Fixed

• Fix coverlet.MTP does not collect coverage on the .NET Framework portion of a large project #​1980 #​1967
• Fix Regression in branch coverage for lambda expressions #​1938
• Fix When using "is" with "or" in pattern matching, branch coverage is lower than normal #​1979
• Fix silent zero coverage on .NET Framework since 8.0.0 #​1985 by @​tobiwae
• Fix Race condition between ProcessExit hit-file write and out-of-proc coverage read causes EndOfStreamException #​1987 #​1988 by @​bkoelman
• Fix Regression TypeInitializationException when targeting .NET Framework - Could not load type 'System.Collections.Concurrent.ConcurrentBag #​2010
• Fix use --config-file CLI arg in coverlet.MTP #​2030 by alexthornton1
• Fix silently empty coverage for shared-framework assemblies missing from compileLibraries #​2032 by @​Eljees

Diff between 10.0.1 and 10.1.0

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

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

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

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

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

• Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider 7.0.3
• Microsoft.Data.SqlClient.Extensions.Azure 7.0.3 — includes the Entra ID authority parsing fix for Dataverse/Dynamics 365 connections.
• Microsoft.Data.SqlClient.Extensions.Abstractions 7.0.3
• Microsoft.Data.SqlClient.Internal.Logging 7.0.3

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.

• edwardneal

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 Microsoft.Data.Sqlite from 10.0.11 to 10.0.14.

Release notes

Sourced from Microsoft.Data.Sqlite's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Hosting.WindowsServices from 10.0.11 to 10.0.14.

Release notes

Sourced from Microsoft.Extensions.Hosting.WindowsServices's releases.

No release notes found for this version range.

Commits viewable in compare view.

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

Release notes

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

18.11.0

What's Changed

• Fix TRX logger mangling astral-plane (non-BMP) characters by @​azat-msft in Fix TRX logger mangling astral-plane (non-BMP) characters microsoft/vstest#16318
• Disable the MTP testhost by default by @​nohwnd in Disable the MTP testhost by default microsoft/vstest#16337
• Fix OS-blind apphost probe in MTP bridge on Unix (regression from #​16201) by @​azat-msft in Fix OS-blind apphost probe in MTP bridge on Unix (regression from #16201) microsoft/vstest#16336
• Retarget the MTP client onto Microsoft.Testing.Platform.ServerMode.Client.Sources by @​nohwnd in Retarget the MTP client onto Microsoft.Testing.Platform.ServerMode.Client.Sources microsoft/vstest#16300
• Pass arguments to PowerShell with -File instead of -command by @​nohwnd in Pass arguments to PowerShell with -File instead of -command microsoft/vstest#16363
• Respect console logger verbosity from a settings file by @​nohwnd in Respect console logger verbosity from a settings file microsoft/vstest#16044
• Fix backslash normalization in VSTestCLIRunSettings on Unix by @​nohwnd in [fix] Fix backslash normalization in VSTestCLIRunSettings on Unix microsoft/vstest#15795
• Docs: fix typo explicitely -> explicitly by @​vaibhav8a in docs: fix typo explicitely -> explicitly microsoft/vstest#16397
• Copy acceptance test diagnostic logs into the test results directory by @​nohwnd in Copy acceptance test diagnostic logs into the test results directory microsoft/vstest#16403

New Contributors

• @​vaibhav8a made their first contribution in docs: fix typo explicitely -> explicitly microsoft/vstest#16397

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

18.10.1

What's Changed

• Isolate code coverage files in published output by @​azat-msft in [rel/18.10] Isolate code coverage files in published output microsoft/vstest#16476

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

18.10.0

What's Changed

• Drop Mono fallback, run .NET Framework tests on Windows only by @​nohwnd in Drop Mono fallback, run .NET Framework tests on Windows only microsoft/vstest#16158
• Run Microsoft.Testing.Platform test apps under vstest.console and datacollector by @​nohwnd in Run Microsoft.Testing.Platform test apps under vstest.console and datacollector microsoft/vstest#16201
• Fix test output eaten by MSBuild terminal logger by @​nohwnd in [fix] Fix test output eaten by MSBuild terminal logger microsoft/vstest#16223
• Remove the experimental test session feature by @​nohwnd in Remove the experimental test session feature microsoft/vstest#16231
• Skip a single bad executor instead of failing all executor loading by @​nohwnd in Skip a single bad executor instead of failing all executor loading microsoft/vstest#16239
• Assert apartment state instead of using Clipboard in UI tests by @​nohwnd in Assert apartment state instead of using Clipboard in UI tests microsoft/vstest#16270
• Surface test host crashes during protocol negotiation by @​nohwnd in Surface test host crashes during protocol negotiation microsoft/vstest#16285
• Pass the inferred target platform to the host in run settings by @​nohwnd in Pass the inferred target platform to the host in run settings microsoft/vstest#16271
• Report raw invalid IsTargetPlatformInferred value, cover host x64 forcing by @​nohwnd in Report raw invalid IsTargetPlatformInferred value, cover host x64 forcing microsoft/vstest#16295
• Disable the MTP testhost by default (#​16337) by @​nohwnd in [rel/18.10] Disable the MTP testhost by default (#16337) microsoft/vstest#16341

Full Changelog: microsoft/vstest@v18.9.0...v18.10.0

Commits viewable in compare view.

Updated Microsoft.SqlServer.DacFx from 170.4.83 to 170.5.96.

Release notes

Sourced from Microsoft.SqlServer.DacFx's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.SqlServer.TransactSql.ScriptDom from 180.78.1 to 180.102.0.

Release notes

Sourced from Microsoft.SqlServer.TransactSql.ScriptDom's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.SqlServer.TransactSql.ScriptDom from 180.78.1 to 180.140.0.

Release notes

Sourced from Microsoft.SqlServer.TransactSql.ScriptDom's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated OpenTelemetry from 1.17.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry's releases.

1.20.1

For highlights and announcements pertaining to this release see: Release Notes > 1.20.1.

The following changes are from the previous release 1.20.0.

• NuGet: OpenTelemetry v1.20.1

  • Fixed a possible race condition on ARM64 when multiple threads record the
    first measurement with no tags, or the first overflow measurement, that could
    cause the measurement to be recorded incorrectly.
    (#​7951)

  • Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
    and prefixed JWTs.
    (#​7955)

  • Fixed default HTTP client log filtering when registering the OTLP log exporter
    through OpenTelemetryLoggerOptions.
    (#​7959)

  • Fixed legacy self-diagnostics logging terminating the process when the log
    file is truncated or the log volume runs out of space.
    (#​7956)

  • Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
    instrumentation suppression, which could cause recursive exports or deadlocks.
    (#​7961)

  • Fixed delta double counters losing subsequent measurements after a non-finite
    or large value and idle metric points with a NaN value failing to be reclaimed.
    (#​7963)

  • Improve the assignment of values to exponential histogram buckets when the
    value is near a bucket boundary by using a pre-computed lookup table.
    (#​7911)

  • Fixed LogRecords being returned to the shared pool while still queued for
    export when an exporter stops enumerating a single-item or array
    Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
    on the same provider to export missing or incorrect data.
    (#​7965)

  • Fixed a SuppressInstrumentationScope.Enter() reference count never being
    released when the Activity it was entered for is not recorded, which caused
    all subsequent telemetry in that execution context to be suppressed.
    (#​7966)

  • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
    or SelfDiagnosticsOptions, are now always created as new files.
    (#​7968)

... (truncated)

1.20.1-rc.1

The following changes are from the previous release 1.20.0.

• NuGet: OpenTelemetry v1.20.1-rc.1

  • Fixed a possible race condition on ARM64 when multiple threads record the
    first measurement with no tags, or the first overflow measurement, that could
    cause the measurement to be recorded incorrectly.
    (#​7951)

  • Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
    and prefixed JWTs.
    (#​7955)

  • Fixed default HTTP client log filtering when registering the OTLP log exporter
    through OpenTelemetryLoggerOptions.
    (#​7959)

  • Fixed legacy self-diagnostics logging terminating the process when the log
    file is truncated or the log volume runs out of space.
    (#​7956)

  • Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
    instrumentation suppression, which could cause recursive exports or deadlocks.
    (#​7961)

  • Fixed delta double counters losing subsequent measurements after a non-finite
    or large value and idle metric points with a NaN value failing to be reclaimed.
    (#​7963)

  • Improve the assignment of values to exponential histogram buckets when the
    value is near a bucket boundary by using a pre-computed lookup table.
    (#​7911)

  • Fixed LogRecords being returned to the shared pool while still queued for
    export when an exporter stops enumerating a single-item or array
    Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
    on the same provider to export missing or incorrect data.
    (#​7965)

  • Fixed a SuppressInstrumentationScope.Enter() reference count never being
    released when the Activity it was entered for is not recorded, which caused
    all subsequent telemetry in that execution context to be suppressed.
    (#​7966)

  • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
    or SelfDiagnosticsOptions, are now always created as new files.
    (#​7968)

  • Self-diagnostics messages written to the sinks configured by
    SelfDiagnosticsOptions are now truncated to 16,384 characters so that the
    ... (truncated)

1.20.1-beta.1

The following changes are from the previous release 1.20.0-beta.1.

• NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.20.1-beta.1

  • Fixed scrape responses being handed to the server in a single write, which
    made the server buffer a full copy of the response for each client that did
    not read it until the request completed or timed out. Responses are now
    written in bounded slices so the server's back-pressure applies.
    (#​7957)

  • Fixed startup scrapes permanently omitting target_info and configured
    resource constant labels from subsequent scrape responses.
    (#​7984)

  • Updated OpenTelemetry core component version(s) to 1.20.1.
    (#​7990)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.20.1-beta.1

  • Fixed scrape responses being handed to the server in a single write, which
    on Linux and macOS made the listener allocate and hold a full copy of the
    response for each client that did not read it until the request completed or
    timed out. Responses are now written in bounded slices.
    (#​7957)

  • Fixed scrape requests that announce a request body holding a thread pool
    thread after their response had been sent on Linux and macOS for as long as
    the client kept trickling in the body. The connection is now closed after
    responding to a request with a body instead of being kept alive.
    (#​7962)

  • Fixed startup scrapes permanently omitting target_info and configured
    resource constant labels from subsequent scrape responses.
    (#​7984)

  • Updated OpenTelemetry core component version(s) to 1.20.1.
    (#​7990)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Shims.OpenTracing v1.20.1-beta.1

  • Updated OpenTelemetry core component version(s) to 1.20.1.
    (#​7990)

  See CHANGELOG for details.

1.20.0

For highlights and announcements pertaining to this release see: Release Notes > 1.20.0.

The following changes are from the previous release 1.19.1.

• NuGet: OpenTelemetry v1.20.0

  • Fixed SuppressInstrumentationScope reference counts leaking between inherited asynchronous execution contexts.
    (#​7803)

  • Self-diagnostic features are explicitly disabled on browser-based platforms (e.g. Blazor) and are now non-functional. Previously, attempting to enable self-diagnostics on such platforms would result in an exception at runtime.
    (#​7799)

  • Added TracerProviderBuilder.ConfigureSampler which receives the resolved Sampler whether set programmatically, via OTEL_TRACES_SAMPLER, or by default, and returns a replacement. Intended for library authors who need to influence sampling without overriding a sampler the application has configured.
    (#​7780)

  • Fixed ResourceBuilder.CreateDefault ignoring OTEL_RESOURCE_ATTRIBUTES and OTEL_SERVICE_NAME environment variables when the host IConfiguration does not contain those settings.
    (#​7855)

  • Added improved self-diagnostics logging to improve the support experience. The new SelfDiagnosticsOptions class configures a rolling file sink and a console sink through the standard options pipeline. Sinks are off by default.
    (#​7588)

  • Fixed a race that could incorrectly route a concurrent metric measurement to the overflow point when its tag set was published as the cardinality limit was reached.
    (#​7804)

  • Added OpenTelemetryLoggerOptions.Version and OpenTelemetryLoggerOptions.SchemaUrl options to set an instrumentation library version and schema URL applied to logs emitted via the Microsoft.Extensions.Logging ILogger integration.
    (#​7727)

  • Fixed LogRecord.CategoryName resetting the current Logger's Version to null when set to a new value.
    (#​7727)

  • Bounded the internal cache of Logger scopes keyed by instrumentation to avoid unbounded growth.
    (#​7727)

  • Fixed the MeterProvider and its IServiceProvider being kept alive after the host is disposed when using Microsoft.Extensions.Diagnostics versions prior to 9.0, which never dispose their MetricsSubscriptionManager (and its underlying MeterListener).
    (#​7924)

  • Fixed a race condition between recording a measurement and collecting a histogram with delta temporality that could cause an empty data point (with a count of zero) to be exported in the next collection cycle.
    (#​7923)

  • Improved metric collection performance after metric streams are removed by compacting metric storage during collection.
    (#​7945)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Api v1.20.0

  • Added Logger.SchemaUrl and a LoggerProvider.GetLogger overload accepting a schema URL parameter using the new LoggerOptions type.
    (#​7727)

  • Breaking change (pre-release only versions): LoggerProvider's protected TryCreateLogger(string? name, out Logger? logger) extensibility method has been replaced by TryCreateLogger(LoggerOptions options, out Logger? logger). Custom LoggerProvider subclasses that override the previous overload must update to override the new one; the old overload is no longer called.
    ... (truncated)

1.20.0-rc.1

The following changes are from the previous release 1.19.1.

• NuGet: OpenTelemetry v1.20.0-rc.1

  • Fixed SuppressInstrumentationScope reference counts leaking between inherited asynchronous execution contexts.
    (#​7803)

  • Self-diagnostic features are explicitly disabled on browser-based platforms (e.g. Blazor) and are now non-functional. Previously, attempting to enable self-diagnostics on such platforms would result in an exception at runtime.
    (#​7799)

  • Added TracerProviderBuilder.ConfigureSampler which receives the resolved Sampler whether set programmatically, via OTEL_TRACES_SAMPLER, or by default, and returns a replacement. Intended for library authors who need to influence sampling without overriding a sampler the application has configured.
    (#​7780)

  • Fixed ResourceBuilder.CreateDefault ignoring OTEL_RESOURCE_ATTRIBUTES and OTEL_SERVICE_NAME environment variables when the host IConfiguration does not contain those settings.
    (#​7855)

  • Added improved self-diagnostics logging to improve the support experience. The new SelfDiagnosticsOptions class configures a rolling file sink and a console sink through the standard options pipeline. Sinks are off by default.
    (#​7588)

  • Fixed a race that could incorrectly route a concurrent metric measurement to the overflow point when its tag set was published as the cardinality limit was reached.
    (#​7804)

  • Added OpenTelemetryLoggerOptions.Version and OpenTelemetryLoggerOptions.SchemaUrl options to set an instrumentation library version and schema URL applied to logs emitted via the Microsoft.Extensions.Logging ILogger integration.
    (#​7727)

  • Fixed LogRecord.CategoryName resetting the current Logger's Version to null when set to a new value.
    (#​7727)

  • Bounded the internal cache of Logger scopes keyed by instrumentation to avoid unbounded growth.
    (#​7727)

  • Fixed the MeterProvider and its IServiceProvider being kept alive after the host is disposed when using Microsoft.Extensions.Diagnostics versions prior to 9.0, which never dispose their MetricsSubscriptionManager (and its underlying MeterListener).
    (#​7924)

  • Fixed a race condition between recording a measurement and collecting a histogram with delta temporality that could cause an empty data point (with a count of zero) to be exported in the next collection cycle.
    (#​7923)

  • Improved metric collection performance after metric streams are removed by compacting metric storage during collection.
    (#​7945)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Api v1.20.0-rc.1

  • Added Logger.SchemaUrl and a LoggerProvider.GetLogger overload accepting a schema URL parameter using the new LoggerOptions type.
    (#​7727)

  • Breaking change (pre-release only versions): LoggerProvider's protected TryCreateLogger(string? name, out Logger? logger) extensibility method has been replaced by TryCreateLogger(LoggerOptions options, out Logger? logger). Custom LoggerProvider subclasses that override the previous overload must update to override the new one; the old overload is no longer called.
    (#​7727)

... (truncated)

1.20.0-beta.1

The following changes are from the previous release 1.19.1-beta.1.

• NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.20.0-beta.1

  • A scrape request whose connection is aborted, or whose X-Prometheus-Scrape-Timeout-Seconds deadline elapses, now stops waiting for an in-progress metrics collection instead of continuing to wait for it to finish. The collection itself is not cancelled and continues running in the background.
    (#​7856)

  • Updated OpenTelemetry core component version(s) to 1.20.0.
    (#​7950)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.20.0-beta.1

  • Updated OpenTelemetry core component version(s) to 1.20.0.
    (#​7950)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Shims.OpenTracing v1.20.0-beta.1

  • Updated OpenTelemetry core component version(s) to 1.20.0.
    (#​7950)

  See CHANGELOG for details.

1.19.1

For highlights and announcements pertaining to this release see: Release Notes > 1.19.1.

The following changes are from the previous release 1.19.0.

• NuGet: OpenTelemetry v1.19.1

  • Fixed NotSupportedException thrown when building a TracerProvider or MeterProvider with a large number of wildcard source/meter patterns on net8.0, and a related OutOfMemoryException that could occur when many such providers were built over the lifetime of a process.
    (#​7788)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Api v1.19.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.19.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.Console v1.19.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.InMemory v1.19.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.19.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.Zipkin v1.19.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Extensions.Hosting v1.19.1

  No notable changes.
  ... (truncated)

1.19.1-rc.1

The following changes are from the previous release 1.19.0.

• NuGet: OpenTelemetry v1.19.1-rc.1

  • Fixed NotSupportedException thrown when building a TracerProvider or MeterProvider with a large number of wildcard source/meter patterns on net8.0, and a related OutOfMemoryException that could occur when many such providers were built over the lifetime of a process.
    (#​7788)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Api v1.19.1-rc.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.19.1-rc.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.Console v1.19.1-rc.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.InMemory v1.19.1-rc.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.19.1-rc.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.Zipkin v1.19.1-rc.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Extensions.Hosting v1.19.1-rc.1

  No notable changes.

  See CHANGELOG for details.
  ... (truncated)

1.19.1-beta.1

The following changes are from the previous release [1.19.0-beta.1](https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/coreunstable-1.19.0...

Description has been truncated

[dependabot]

Labels

The following labels could not be found: dependencies, nuget. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.