Bump the non-major-versions group with 4 updates #187

Forwarded Headers Middleware: Ignore X-Forwarded-Headers from Unknown Proxy (#61623)
The Forwarded Headers Middleware now ignores X-Forwarded-Headers sent from unknown proxies. This change improves security by ensuring that only trusted proxies can influence the forwarded headers, preventing potential spoofing or misrouting of requests.

Dependency Updates

Update dependencies from dotnet/arcade (#61832)
This update brings in the latest changes from the dotnet/arcade repository, ensuring that ASP.NET Core benefits from recent improvements, bug fixes, and security patches in the shared build infrastructure.
Bump src/submodules/googletest from 52204f7 to 04ee1b4 (#61761)
The GoogleTest submodule has been updated to a newer commit, providing the latest testing features, bug fixes, and performance improvements for the project's C++ test components.

Miscellaneous

Update branding to 8.0.17 (#61830)
The project version branding has been updated to reflect the new 8.0.17 release, ensuring consistency across build outputs and documentation.
Merging internal commits for release/8.0 (#61924)
This change merges various internal commits into the release/8.0 branch, incorporating minor fixes, documentation updates, and other non-user-facing improvements to keep the release branch up to date.

This summary is generated and may contain inaccuracies. For complete details, please review the linked pull requests.

Full Changelog: dotnet/aspnetcore@v8.0.16...v8.0.17

8.0.16

Release

What's Changed

Update branding to 8.0.16 by @vseanreesermsft in Update branding to 8.0.16 dotnet/aspnetcore#61283
[release/8.0] (deps): Bump src/submodules/googletest from 24a9e94 to 52204f7 by @dependabot in [release/8.0] (deps): Bump src/submodules/googletest from 24a9e94 to 52204f7 dotnet/aspnetcore#61260
[release/8.0] Update dependencies from dotnet/source-build-externals by @dotnet-maestro in [release/8.0] Update dependencies from dotnet/source-build-externals dotnet/aspnetcore#61281
[release/8.0] Upgrade to Ubuntu 22 by @wtgodbe in [release/8.0] Upgrade to Ubuntu 22 dotnet/aspnetcore#61216
[release/8.0] Update dependencies from dotnet/arcade by @dotnet-maestro in [release/8.0] Update dependencies from dotnet/arcade dotnet/aspnetcore#60901
[release/8.0] Update dependencies from dotnet/source-build-reference-packages by @dotnet-maestro in [release/8.0] Update dependencies from dotnet/source-build-reference-packages dotnet/aspnetcore#60926
[release/8.0] Update dependencies from dotnet/arcade by @dotnet-maestro in [release/8.0] Update dependencies from dotnet/arcade dotnet/aspnetcore#61404
Merging internal commits for release/8.0 by @vseanreesermsft in Merging internal commits for release/8.0 dotnet/aspnetcore#61398
[release/8.0] Update dependencies from dotnet/arcade by @dotnet-maestro in [release/8.0] Update dependencies from dotnet/arcade dotnet/aspnetcore#61411
Revert "Revert "[release/8.0] Update remnants of azureedge.net"" by @wtgodbe in Revert "Revert "[release/8.0] Update remnants of azureedge.net"" dotnet/aspnetcore#60352
[release/8.0] Fix preserving messages for stateful reconnect with backplane by @BrennanConroy in [release/8.0] Fix preserving messages for stateful reconnect with backplane dotnet/aspnetcore#61375
[release/8.0] Update dependencies from dotnet/source-build-reference-packages by @dotnet-maestro in [release/8.0] Update dependencies from dotnet/source-build-reference-packages dotnet/aspnetcore#61442
fetch TLS client hello message from HTTP.SYS by @BrennanConroy in fetch TLS client hello message from HTTP.SYS dotnet/aspnetcore#61494

Full Changelog: dotnet/aspnetcore@v8.0.15...v8.0.16

Commits viewable in compare view.

Updated Microsoft.Data.SqlClient from 6.0.2 to 6.1.3.

Release notes

Sourced from Microsoft.Data.SqlClient's releases.

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

6.1.1

This update includes the following changes since the 6.1.0 release:

Fixed

Reverted changes related to improving partial packet detection, fixup, and replay functionality. This revert addresses regressions introduced in 6.1.0. (#3556)
Applied reference assembly corrections supporting vector, fixed JSON tests, and ensured related tests are enabled. #3562
Fixed SqlVector<T>.Null API signature in Reference assembly. #3521

Changed

Upgraded Azure.Identity and other dependencies to newer versions. (#3538) (#3552)

6.1.0

Release Notes

[!WARNING]
This release version is delisted from NuGet.org and is no longer supported.
It contains critical bugs that make it unsuitable for use.

Stable Release 6.1.0 - 2025-07-25

This update brings the following changes since the 6.0.2 stable release:

Added

Added dedicated SQL Server vector datatype support

What Changed:

Optimized vector communications between MDS and SQL Server 2025, employing a custom binary format over the TDS protocol. (#3433, #3443)
Reduced processing load compared to existing JSON-based vector support.
Initial support for 32-bit single-precision floating point vectors.

Who Benefits:

Applications moving large vector data sets will see beneficial improvements to processing times and memory requirements.
Vector-specific APIs are ready to support future numeric representations with a consistent look-and-feel.

Impact:

Reduced transmission and processing times for vector operations versus JSON using SQL Server 2025 preview:
- Reads: 50x improvement
- Writes: 3.3x improvement
- Bulk Copy: 19x improvement
- (Observed with vector column of max 1998 size, and 10,000 records for each operation.)
Improved memory footprint due to the elimination of JSON serialization/deserialization and string representation bloat.
For backwards compatibility with earlier SQL Server Vector implementations, applications may continue to use JSON strings to send/receive vector data, although they will not see any of the performance improvements noted above.

Revived .NET Standard 2.0 target support

What Changed:

Support for targeting .NET Standard 2.0 has returned. (#3381)
Support had previously been removed in the 6.0 release, with the community voicing concerns.

Who Benefits:

Libraries that depend on MDS may seamlessly target any of the following frameworks:
- .NET Standard 2.0
- .NET Framework 4.6.2 and above
- .NET 8.0
- .NET 9.0
Applications should continue to target runtimes.
... (truncated)

6.1.0-preview2

Preview Release 6.1.0-preview2.25178.5 - 2025-06-27

This update brings the following changes since the 6.1.0-preview1 release:

Added

Added dedicated SQL Server vector datatype support

What Changed:

Optimized vector communications between MDS and SQL Server 2025, employing a custom binary format over the TDS protocol. (#3433, #3443)
Reduced processing load compared to existing JSON-based vector support.
Initial support for 32-bit single-precision floating point vectors.

Who Benefits:

Applications moving large vector data sets will see beneficial improvements to processing times and memory requirements.
Vector-specific APIs are ready to support future numeric representations with a consistent look-and-feel.

Impact:

Reduced transmission and processing times for vector operations versus JSON using SQL Server 2025 preview:
- Reads: 50x improvement
- Writes: 3.3x improvement
- Bulk Copy: 19x improvement
- (Observed with vector column of max 1998 size, and 10,000 records for each operation.)
Improved memory footprint due to the elimination of JSON serialization/deserialization and string representation bloat.
For backwards compatibility with earlier SQL Server Vector implementations, applications may continue to use JSON strings to send/receive vector data, although they will not see any of the performance improvements noted above.

Revived .NET Standard 2.0 target support

What Changed:

Support for targeting .NET Standard 2.0 has returned. (#3381)
Support had previously been removed in the 6.0 release, with the [community voicing concerns] (Microsoft.Data.SqlClient 6.0 and .Net Standard dotnet/SqlClient#3115).

Who Benefits:

Libraries that depend on MDS may seamlessly target any of the following frameworks:
- .NET Standard 2.0
- .NET Framework 4.6.2 and above
- .NET 8.0
- .NET 9.0
Applications should continue to target runtimes.
- The MDS .NET Standard 2.0 target framework support does not include an actual implementation, and cannot be used with a runtime.
- An application's build/publish process should always pick the appropriate MDS .NET/.NET Framework runtime implementation.
- Custom build/publish actions that incorrectly try to deploy the MDS .NET Standard 2.0 reference DLL at runtime are not supported.

Impact:

... (truncated)

6.1.0-preview1

This update brings the following changes over the previous release:

Added

Added packet multiplexing support to improve large data read performance. #2714 #3161 #3202
Added support for special casing with Fabric endpoints. #3084

Fixed

Fixed distributed transactions to be preserved during pooled connection resets. #3019.
Fixed application crash when the Data Source parameter begins with a comma. #3250.
Resolved synonym count discrepancies in debug mode. #3098.
Addressed warnings for down-level SSL/TLS versions. #3126.

Changed

Optimized binary size for AOT. #3091
Refined bulk copy operations to handle unmatched column names more effectively. #3205.
Enhanced SqlBulkCopy to explicitly identify mismatched column names. #3183.
Optimized outgoing SSPI blob handling using IBufferWriter<byte>. #2452.
Replaced byte[] with string for SNI to improve efficiency. #2790.
Code cleanup to remove SQL 2000 support #2839, #3206, #3217,
Connection pool design refactor for a modular connection pool design #3199
Updated various dependencies #3229, primarily:
- System.Text.Encodings.Web to v8.0.0
- System.Text.Json to v8.0.5
- Azure.Identity to v1.13.2
- Microsoft.Identity.Model.Json.Web.Tokens to v7.7.1
- Microsoft.Identity.Model.Protocols.OpenIdConnect to v7.7.1
Code merge towards a unified SqlClient project, aligning .NET Framework and .NET Core implementations. (#2957, #2963, #2984, #2982, #3023, #3015, #2967, #3164, #3163, #3171, #3182, #3179, #3156, #3213, #3232, #3236, #3231, #3241, #3246, #3247, #3222, #3255, #3254, #3259, #3264, #3256, #3251, #3275, #3277, #3263, #3292, #3208).
Test improvements include updates to test references, removal of hardcoded certificates, improved stability, and better coverage (#3041, #3034, #3130, #3128, #3181, #3060, #3184, #3033, #3186, #3025, #3230, #3237, #3059, #3061).

New Contributors

@emmanuel-ferdman made their first contribution in Update DockerLinuxTest/Program.cs reference dotnet/SqlClient#3041
@MaceWindu made their first contribution in Fix typo in Update 6.0.0-preview1.md dotnet/SqlClient#3134
@JNjenga made their first contribution in SqlBulkCopy: Explicitly state column name that mismatches(#3170) dotnet/SqlClient#3183
@Midhunnnk made their first contribution in Fix crash when Data Source starts with a comma dotnet/SqlClient#3250

6.0.4

This update brings the below changes over the 6.0.3 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 #3703.

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.

Target Platform Support

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

Dependencies

.NET Framework

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.5.0
Microsoft.IdentityModel.Protocols.OpenIdConnect 7.5.0
System.Buffers 4.5.1
System.Security.Cryptography.Pkcs 8.0.1
System.Text.Encodings.Web 8.0.0
System.Text.Json 8.0.5
System.Data.Common 4.3.0

.NET 8

Azure.Identity 1.14.2
... (truncated)

6.0.3

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

Fixed

Fixed an issue where a Custom SqlClientAuthenticationProvider was being overwritten by default implementation. #3652
Fixed a concurrency issue in connection pooling where the number of active connections could be lower than the configured maximum pool size. #3654

Changed

Updated MSAL usage as per code compliance requirements #3360
Updated SqlDecimal implementation to improve code compliance #3466
Updated Azure.Identity and related dependencies #3553

Commits viewable in compare view.

Updated Microsoft.Data.Sqlite from 9.0.4 to 10.0.0.

Release notes

Sourced from Microsoft.Data.Sqlite's releases.

10.0.0-preview.6.25358.103

You can build .NET 10.0 Preview 6 from the repository by cloning the release tag v10.0.0-preview.6.25358.103 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.