Bump the version-updates group with 3 updates#148
Merged
github-actions[bot] merged 1 commit intoJun 16, 2026
Merged
Conversation
Bumps Asm.AspNetCore.Api from 3.8.143 to 3.8.151 Bumps Asm.OAuth from 3.8.143 to 3.8.151 Bumps Azure.Core from 1.58.0 to 1.59.0 --- updated-dependencies: - dependency-name: Asm.AspNetCore.Api dependency-version: 3.8.151 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: version-updates - dependency-name: Asm.OAuth dependency-version: 3.8.151 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: version-updates - dependency-name: Azure.Core dependency-version: 1.59.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: version-updates ... Signed-off-by: dependabot[bot] <support@github.com>
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.
Updated Asm.AspNetCore.Api from 3.8.143 to 3.8.151.
Release notes
Sourced from Asm.AspNetCore.Api's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Asm.OAuth from 3.8.143 to 3.8.151.
Release notes
Sourced from Asm.OAuth's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Azure.Core from 1.58.0 to 1.59.0.
Release notes
Sourced from Azure.Core's releases.
1.59.0
1.59.0 (2026-06-09)
Features Added
AZID0004) mTLS Proof-of-Possession token binding support for managed identity scenarios, including dynamic host capability detection via MSAL and transport certificate rotation APIs onBearerTokenAuthenticationPolicy.Bugs Fixed
BearerTokenAuthenticationPolicyso that theAuthorizationheader is no longer re-attached to a request that has been redirected to a different host. Previously,RedirectPolicywould strip theAuthorizationheader before following a redirect, but the per-retryBearerTokenAuthenticationPolicywould re-add the cached bearer token to the redirected request — including when the redirect target was a different host. The policy now detects when the request URI authority has changed since it last authorized the message, defensively strips anyAuthorizationheader, and skips both re-authorization and theWWW-Authenticate(CAE)401handler so that no bearer token is sent to — or fetched in response to a challenge from — the redirect target. Same-host redirects, normal (non-redirected) requests, and CAE handling against the original host are unchanged. Callers who explicitly enabled auto-redirect (viaHttpPipelineTransportOptions.IsClientRedirectEnabled = trueorRedirectPolicy.SetAllowAutoRedirect(message, true)) and depended on the bearer token being re-attached on cross-host redirects should construct a separate client targeting the redirect-target host with a credential bound to that host's resource.Other Changes
Microsoft.Identity.Clientdependency to4.84.2.Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions