[6.1.6] Set SqlClient 6.1.6 version numbers#4394
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Prepares the release/6.1 branch for the 6.1.6 release by updating centralized version variables/props and aligning the AKV provider’s SqlClient dependency range accordingly.
Changes:
- Updated OneBranch pipeline version variables to
6.1.6and advanced the preview test build version to6.1.7-preview1. - Bumped
MdsVersionDefaultto6.1.6for package/assembly versioning. - Updated the AKV provider
.nuspecto depend onMicrosoft.Data.SqlClient[6.1.6,7.0.0)and moved StressTests’ pinned package version to the latest published6.1.5.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| eng/pipelines/onebranch/variables/common-variables.yml | Bumps patch to 6.1.6 and advances preview version for test preview builds. |
| tools/props/Versions.props | Updates the default SqlClient version used for package/assembly versioning to 6.1.6. |
| tools/specs/add-ons/Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider.nuspec | Aligns AKV provider dependency range to require SqlClient 6.1.6+. |
| src/Microsoft.Data.SqlClient/tests/StressTests/Directory.Packages.props | Pins StressTests to the latest published package version when CI override isn’t provided. |
cheenamalhotra
previously approved these changes
Jun 23, 2026
paulmedynski
approved these changes
Jun 24, 2026
priyankatiwari08
approved these changes
Jun 24, 2026
cheenamalhotra
approved these changes
Jun 24, 2026
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.
Description
Sets the version numbers in preparation for the 6.1.6 release (and the AKV Provider 6.1.3 release), following the same pattern as #4162 (6.1.5).
Changes
Microsoft.Data.SqlClient (6.1.6)
common-variables.yml: bumpedPatch5→6; updatedPreviewNugetPackageVersion6.1.6-preview1→6.1.7-preview1Versions.props:MdsVersionDefault6.1.5→6.1.6Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider.nuspec: MDS dependency[6.1.5,7.0.0)→[6.1.6,7.0.0)(all TFM groups)Directory.Packages.props:MdsVersion6.1.4→6.1.5(last published version)Azure Key Vault Provider (6.1.3)
common-variables.yml: bumpedakvVersionPatch2→3The last published AKV version (6.1.2) only enabled strong-name signing. Since then the provider has accrued a dependency refresh ([6.1] Dependency Cleanup #3843 —
Azure.Core1.47.1 → 1.50.0,Azure.Security.KeyVault.Keys4.7.0 → 4.8.0,Microsoft.Extensions.Caching.Memory→ 9.0.11, removed unusedSystem.Text.Encodings.Web, pinned dependency versions) and build fixes ([6.1] Fixes build issues for AKV Provider #4250 — strong-name signing now keys offSigningKeyPath). These are packaging/dependency changes only; no functional or API changes. Since 6.1.2 is already on NuGet, the version must move to 6.1.3.Notes
Azure.Core1.50.0,Microsoft.Extensions.Caching.Memory) match across all target frameworks — no version conflicts.