Bump Azure.Core from 1.59.0 to 1.60.0#3850
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Member
|
@dependabot rebase |
--- updated-dependencies: - dependency-name: Azure.Core dependency-version: 1.60.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/nuget/src/PSRule.Rules.Azure.Patterns/Azure.Core-1.60.0
branch
from
b354a71 to
fe7f439
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
1 participant
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.
Updated Azure.Core from 1.59.0 to 1.60.0.
Release notes
Sourced from Azure.Core's releases.
1.60.0
1.60.0 (2026-06-30)
Features Added
AZID0004)DisableMtlsProofOfPossessionproperty toManagedIdentityCredentialOptionsto allow explicit opt-out of mTLS proof-of-possession token acquisition when the underlying requirements are met.Microsoft.Identity.Client.KeyAttestationextension package.Bugs Fixed
DefaultAzureCredentialcould throw anAuthenticationFailedExceptionand stop evaluating the credential chain on hosts without a managed identity — for example, a developer machine running in Visual Studio where the IMDS endpoint (169.254.169.254) is unreachable. WhenManagedIdentityCredentialis part of a chain, a failure to detect the managed identity source/capabilities is now surfaced as aCredentialUnavailableException, allowing the chain to continue to the next credential.Commits viewable in compare view.