Bump Microsoft.Data.SqlClient to 7.0.1 (+ Extensions.Azure for Entra)#895
Merged
erikdarlingdata merged 1 commit intodevfrom Apr 25, 2026
Merged
Bump Microsoft.Data.SqlClient to 7.0.1 (+ Extensions.Azure for Entra)#895erikdarlingdata merged 1 commit intodevfrom
erikdarlingdata merged 1 commit intodevfrom
Conversation
SqlClient 7.0 split Azure/Entra dependencies out of the core package, so projects with Entra-Interactive auth paths (ActiveDirectoryInteractive) also need the new Microsoft.Data.SqlClient.Extensions.Azure helper to keep MFA login working at runtime. Bumps to 7.0.1 across: - Dashboard (+ Extensions.Azure 1.0.0) - Lite (+ Extensions.Azure 1.0.0) - Installer.Core (+ Extensions.Azure 1.0.0; transitive via Installer/InstallerGui/Installer.Tests) - InstallerGui (+ Extensions.Azure 1.0.0) - Installer (no Extensions.Azure — no Entra path) - Installer.Tests (no Extensions.Azure — no Entra path) Connection strings already set Encrypt explicitly everywhere, so the 4.0-era default flip is a no-op for this repo. SQL Server 2012+ remains supported (so all of 2016/2017/2019/2022/2025 stay reachable). Verified: - All six projects build clean - Installer.Tests: 46/46 passing against real SQL - Lite.Tests: 257/257 passing against real SQL - Dashboard and Lite launch and stay running Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
69830e2 to
90907b4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Major-version bump of
Microsoft.Data.SqlClientfrom 6.1.4 → 7.0.1. The breaking change in 7.0 is that Azure/Entra dependencies were split out of the core package — anything usingSqlAuthenticationMethod.ActiveDirectory*now requires the separateMicrosoft.Data.SqlClient.Extensions.Azurepackage, or it throws at runtime (compile still succeeds, so the regression is silent without it).We use
ActiveDirectoryInteractivein five places (Dashboard/Lite/Installer.Core), so this PR addsMicrosoft.Data.SqlClient.Extensions.Azure 1.0.0to those projects. Pure-SQL-auth projects (Installer,Installer.Tests) get the SqlClient bump only.7.0.1 specifically (not 7.0.0): patches a
SqlBulkCopyregression against SQL 2016 — we don't useSqlBulkCopy, but no reason to land on 7.0.0.Why this is low-risk for us
Encryptexplicitly (the only behavioral default flip in recent SqlClient history) — no silent change.SqlBulkCopy,SqlDependency,ColumnEncryption, customSqlAuthenticationProvider, orServerCertificateValidationCallback.Test plan
Installer.Tests: 46/46 passing (exercises real SqlClient against test SQL servers)Lite.Tests: 257/257 passing (exercises real SqlClient)Encrypt=Mandatory, TrustServerCertificate=trueand confirm a collection cycle completesExtensions.Azurewould silently regressInstallerend-to-end against a fresh database🤖 Generated with Claude Code