Bump the version-updates group with 3 updates - #204
Merged
github-actions[bot] merged 1 commit intoSep 29, 2026
Merged
github-actions[bot] merged 1 commit into
github-actions[bot] merged 1 commit into
Conversation
Bumps Asm.AspNetCore.Api from 5.1.10 to 5.1.23 Bumps Asm.OAuth from 5.1.10 to 5.1.23 Bumps Azure.Core from 1.62.0 to 1.63.0 --- updated-dependencies: - dependency-name: Asm.AspNetCore.Api dependency-version: 5.1.23 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: version-updates - dependency-name: Asm.OAuth dependency-version: 5.1.23 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: version-updates - dependency-name: Azure.Core dependency-version: 1.63.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: version-updates ... Signed-off-by: dependabot[bot] <support@github.com>
github-actions
Bot
deleted the
dependabot/nuget/src/KeyLens.Api/version-updates-bde2e74397
branch
September 29, 2026 22:07
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 5.1.10 to 5.1.23.
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 5.1.10 to 5.1.23.
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.62.0 to 1.63.0.
Release notes
Sourced from Azure.Core's releases.
1.63.0
1.63.0 (2026-09-25)
Features Added
ClientCertificateCredential, including subject name and issuer certificate authentication configured withSendCertificateChain. Proof-of-possession is used by default when requested; first-party applications can opt out by setting theAzure.Identity.EnableClientCertificateMtlsProofOfPossessionAppContext switch (orAZURE_IDENTITY_ENABLE_CLIENT_CERTIFICATE_MTLS_POPenvironment variable) tofalse.EnableMtlsProofOfPossessiontofalsein the credential's JSON configuration to force bearer authentication for both exchanges. On a host that cannot provide a binding certificate, the flow falls back to a bearer token instead of failing, matching the direct managed identity flow.Breaking Changes
ManagedIdentityCredentialOptions.DisableMtlsProofOfPossessionproperty and corresponding configuration setting toEnableMtlsProofOfPossession. mTLS proof-of-possession is enabled by default for direct and configured managed identity when requested and supported. To force bearer authentication, replaceDisableMtlsProofOfPossession = truewithEnableMtlsProofOfPossession = falsein code or credential configuration.Bugs Fixed
ModelReaderWriterdeserialization ofGeoPointwithAzureCoreContextor a generated consumer context throwing because its type builder was not registered.DefaultAzureCredentialtaking up to a minute to continue past managed identity on hosts where IMDS is unavailable. Ordinary chained requests use the short Azure.Core IMDS probe, while proof-of-possession capability discovery passes the same initial IMDS timeout to MSAL so discovery retry delays are canceled and timed-out discovery results are not cached.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