Skip to content

Update Azure.Identity and other dependencies #3538

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Aug 8, 2025

Conversation

cheenamalhotra
Copy link
Member

Addresses #3509
(needs to be back-ported to release/6.1, release/6.0, and release/5.1)

@Copilot Copilot AI review requested due to automatic review settings August 2, 2025 07:47
@cheenamalhotra cheenamalhotra requested a review from a team as a code owner August 2, 2025 07:47
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates Azure-related dependencies to newer versions, addressing issue #3509. The update includes upgrading Azure.Identity, Azure.Core, and Azure.Security.KeyVault.Keys packages across multiple project files and adding pragma warnings to suppress obsolete method warnings.

  • Updated Azure.Identity from version 1.13.2 to 1.14.2 across all target frameworks
  • Updated Azure.Core from version 1.38.0/1.44.1 to 1.46.1 and Azure.Security.KeyVault.Keys from 4.5.0 to 4.7.0
  • Added pragma warnings to suppress obsolete method warnings for AcquireTokenByIntegratedWindowsAuth

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider.nuspec Updates Azure.Core and Azure.Security.KeyVault.Keys dependency versions
Microsoft.Data.SqlClient.nuspec Updates Azure.Identity dependency version across all target frameworks
ActiveDirectoryAuthenticationProvider.cs Adds pragma warnings to suppress obsolete method warnings
Directory.Packages.props Updates centralized package version definitions for Azure dependencies

@cheenamalhotra cheenamalhotra added this to the 6.1.1 milestone Aug 2, 2025
@apoorvdeshmukh apoorvdeshmukh added the Triage Needed 🆕 For new issues, not triaged yet. label Aug 4, 2025
Copy link
Contributor

@paulmedynski paulmedynski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use latest version of Azure.Core if possible.

@cheenamalhotra cheenamalhotra requested review from paulmedynski and a team August 5, 2025 20:13
@cheenamalhotra cheenamalhotra removed the Triage Needed 🆕 For new issues, not triaged yet. label Aug 7, 2025
@Frulfump
Copy link

Frulfump commented Aug 8, 2025

LGTM, thanks for getting this sorted!

(If the intent with the description comment "Addresses # 3509" was to auto-link the PR to the issue it won't work and must use these keywords instead https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)

EDIT: N.b
https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#about-linked-issues-and-pull-requests

The special keywords in a pull request description are interpreted only when the pull request targets the repository's default branch. If the pull request targets any other branch, then these keywords are ignored, no links are created, and merging the PR has no effect on the issues.

@cheenamalhotra cheenamalhotra merged commit a493bde into main Aug 8, 2025
244 of 250 checks passed
@cheenamalhotra cheenamalhotra deleted the dev/cheena/az-identity-update branch August 8, 2025 16:43
@cheenamalhotra cheenamalhotra modified the milestones: 6.1.1, 7.0-preview1 Aug 8, 2025
This was referenced Aug 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6.0.2 (6.1.0) dependent on deprecated Azure.Identity version 1.11.4 (1.13.2)
6 participants