Bump the graph-identity-telemetry group with 1 update - #574
Merged
drmoisan merged 1 commit intoAug 21, 2026
Merged
Conversation
Reapplies the substantive change of the graph-identity-telemetry Dependabot group on top of main. The original commit could not be rebased: its NuGet regeneration collapsed app.config and packages.config onto single lines, which conflicted with the CSharpier-formatted tree that PR #573 restored. The bump is applied in three places per project, scoped to the Azure.Core element so no sibling assembly version is rewritten: - packages.config package version 1.61.0 -> 1.62.0 - *.csproj Reference assembly version and HintPath - app.config bindingRedirect 1.61.0.0 -> 1.62.0.0 Two deliberate differences from the Dependabot commit: - the `processorArchitecture=MSIL` attribute on the Azure.Core Reference is preserved; Dependabot dropped it. - the binding redirect is also advanced in the six non-test projects that carry the redirect without a direct package reference (QuickFiler, Tags, TaskMaster, TaskTree, TaskVisualization, ToDoModel). Dependabot left those at 1.61.0.0, which would redirect to an assembly version no longer present in packages/. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016LdWAA7aMkzJ27NUW7WzaT
drmoisanforce-pushed
the
dependabot/nuget/QuickFiler.Test/graph-identity-telemetry/Azure.Core-74a048c980
branch
from
August 21, 2026 19:37
7067425 to
969441fCompareContributorAuthor
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
Uh oh!
There was an error while loading. Please reload this page.
dependabotBot
deleted the
dependabot/nuget/QuickFiler.Test/graph-identity-telemetry/Azure.Core-74a048c980
branch
August 21, 2026 20:07
5 tasks
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 freeto 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.61.0 to 1.62.0.
Release notes
Sourced from Azure.Core's releases.
1.62.0
1.62.0 (2026-08-20)
Features Added
SCME0002)AzureCredentialResolver.Defaultpublic static property so standalone callers can share the process-wide credential cache used by DI-resolved paths.AzureCredentialResolvernow resolves everyChainedTokenCredentialSources[]entry through the active resolver chain, so any registeredCredentialResolver(built-in, broker, or third-party) can claim or override an entry. Entries are constructed as chained, so transient failures surface asCredentialUnavailableExceptionand the chain falls through.Breaking Changes
AzureCredentialResolvernow resolves a top-level single source (e.g.CredentialSource: AzureCliCredential) to the concrete credential type (AzureCliCredential) rather than aDefaultAzureCredentialwrapper. Construction is unchanged (it uses the sameDefaultAzureCredentialFactoryhelpers) — only the returned type differs; callers usingCredentialSettings.TokenProvideras aTokenCredentialare unaffected.AzureCredentialResolverno longer claims top-levelBrokerCredentialsections (canonical name orbrokeralias); they now requireBrokerCredentialResolverfromAzure.Identity.Broker1.7.0+ (e.g. viaAddBrokerCredentialResolver()).BrokerCredentialentries nested inside aChainedTokenCredentialcontinue to resolve. Note: ifBrokerCredentialResolverfromAzure.Identity.Broker1.7.0 is registered ahead ofAzureCredentialResolver, a nestedBrokerCredentialentry is currently built as non-chained, so it may surfaceAuthenticationFailedExceptionand abort the chain instead of falling through to the next entry. Without a broker resolver registered, the built-in chain path builds the broker entry as chained (correct fall-through). A futureAzure.Identity.Brokerrelease will make its resolver honor chained semantics for nested entries.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