-
Notifications
You must be signed in to change notification settings - Fork 3
chore(deps): update nuget non-major dependencies #29
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
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/nuget-minor-patch
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
0eff104 to
7b90e49
Compare
7b90e49 to
9d2f822
Compare
76bea55 to
d751925
Compare
af97495 to
ae89b46
Compare
ae89b46 to
e0312af
Compare
eddcbc0 to
a343ba7
Compare
a343ba7 to
f17b0fc
Compare
9ec9df6 to
b0bd68d
Compare
b0bd68d to
432c9c5
Compare
432c9c5 to
b5af283
Compare
b5af283 to
7eecc7f
Compare
7eecc7f to
893d51a
Compare
893d51a to
5b52364
Compare
60d4295 to
4e92353
Compare
4e92353 to
0202879
Compare
a84a846 to
b2f1eae
Compare
b2f1eae to
4009240
Compare
c22ae7b to
83e2f40
Compare
02c6bc5 to
c2e9dc9
Compare
c2e9dc9 to
8867888
Compare
8867888 to
d468953
Compare
d468953 to
ce2205e
Compare
ce2205e to
fa8ceb4
Compare
1cca7d7 to
4cc99ba
Compare
9c55913 to
6395b72
Compare
6395b72 to
d8e3e72
Compare
d8e3e72 to
4782237
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.
This PR contains the following updates:
1.12.0->1.17.04.6.0->4.8.04.6.0->4.8.02.2.5->2.3.08.1.0->8.14.08.1.0->8.14.04.4.1->4.6.08.1.0->8.14.0Release Notes
Azure/azure-sdk-for-net (Azure.Identity)
v1.17.0Compare Source
1.17.0 (2025-10-07)
Bugs Fixed
WithTenantIdinstead ofWithTenantIdFromAuthorityto prevent malformed Uris to the authority.Other Changes
BrowserCustomizationOptions.UseEmbeddedWebViewproperty. This option requires additional dependencies on Microsoft.Identity.Client.Desktop and is no longer supported. Consider using brokered authentication instead.v1.16.0Compare Source
1.16.0 (2025-09-09)
Features Added
DefaultAzureCredentialconstructor that accepts a custom environment variable name for credential configuration. This provides flexibility beyond the defaultAZURE_TOKEN_CREDENTIALSenvironment variable. The constructor accepts any environment variable name and uses the same credential selection logic as the existingAZURE_TOKEN_CREDENTIALSprocessing.DefaultAzureCredential.DefaultEnvironmentVariableNameconstant property that returns"AZURE_TOKEN_CREDENTIALS"for convenience when referencing the default environment variable name.AzureCliCredential,AzurePowerShellCredential, andAzureDeveloperCliCredentialnow throw anAuthenticationFailedExceptionwhen theTokenRequestContextincludes claims, as these credentials do not support claims challenges. The exception message includes guidance for handling such scenarios.AZURE_TOKEN_CREDENTIALSor the equivalent custom environment variable is configured toManagedIdentityCredential, theDefaultAzureCredentialdoes not issue a probe request and performs retries with exponential backoff.Bugs Fixed
AzureDeveloperCliCredentialhanging when theAZD_DEBUGenvironment variable is set by adding the--no-promptflag to prevent interactive prompts (#52005).BrokerCredentialis now included in the chain whenAZURE_TOKEN_CREDENTIALSis set todev.DefaultAzureCredentialthat caused the credential chain to be constructed incorrectly when using AZURE_TOKEN_CREDENTIALS in combination withDefaultAzureCredentialOptions.Other Changes
BrokerCredentialis now always included in theDefaultAzureCredentialchain. If theAzure.Identity.Brokerpackage is not referenced, an exception will be thrown whenGetTokenis called, making its behavior consistent with the rest of the credentials in the chain.Microsoft.Identity.Clientdependency to version 4.76.0.Microsoft.Identity.Client.Extensions.Msaldependency to version 4.76.0.v1.15.0Compare Source
1.15.0 (2025-08-07)
Breaking Changes
Behavioral Breaking Changes
SharedTokenCacheCredential. The supporting credential (SharedTokenCacheCredential) was a legacy mechanism for authenticating clients using credentials provided to Visual Studio. For brokered authentication, consider usingInteractiveBrowserCredentialinstead. The following changes have been made:SharedTokenCacheCredentialclass is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheCredentialOptionsclass is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]DefaultAzureCredentialOptions.ExcludeSharedTokenCacheCredentialproperty is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheUsernameproperty is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheCredentialis no longer included in theDefaultAzureCredentialauthentication flowBugs Fixed
AdditionallyAllowedTenantsvalues which will now be matched against tenant IDs without case sensitivity, making the authentication more resilient to case differences in tenant IDs returned from WWW-Authenticate challenges (#51693).Other Changes
BrokerAuthenticationCredentialhas been renamed asBrokerCredential.Added the
EditorBrowsable(Never)attribute to propertyVisualStudioCodeTenantIdasTenantIdis preferred. TheVisualStudioCodeTenantIdproperty exists only to provide backwards compatibility.v1.14.2Compare Source
1.14.2 (2025-07-10)
Other changes
Microsoft.Identity.Clientdependency to version 4.73.1v1.14.1Compare Source
1.14.1 (2025-07-08)
Bugs Fixed
v1.14.0Compare Source
1.14.0 (2025-05-13)
Other Changes
Username,Password,AZURE_USERNAME, andAZURE_PASSWORDin XML comments fromEnvironmentCredentialOptionsandEnvironmentCredentialdue to lack of MFA support. See MFA enforcement details.AZURE_USERNAMEandAZURE_PASSWORDas obsolete due to lack of MFA support. See MFA enforcement details.AZURE_TOKEN_CREDENTIALSenvironment variable toDefaultAzureCredential, which allows for choosing between 'deployed service' and 'developer tools' credentials. Valid values are 'dev' for developer tools and 'prod' for deployed service.v1.13.2Compare Source
1.13.2 (2025-01-14)
Bugs Fixed
DefaultAzureCredentialOptions.TenantIdtwice throws anInvalidOperationException(#47035)ManagedIdentityCredentialdoes not honor theCancellationTokenpassed toGetTokenandGetTokenAsync. (#47156)DefaultAzureCredentialwould not fall through to the next credential in the chain under certain exception conditions.ManagedIdentityCredentialwhen used in aChainedTokenCredentialwhere the invalid json responses do not fall through to the next credential in the chain. (#47470)v1.13.1Compare Source
1.13.1 (2024-10-24)
Bugs Fixed
ManagedIdentityCredentialfrom attempting to detect if Workload Identity is enabled in the current environment. #46653DefaultAzureCredentialfrom progressing pastManagedIdentityCredentialin some scenarios where the identity was not available. #46709v1.13.0Compare Source
1.13.0 (2024-10-14)
Features Added
ManagedIdentityCredentialnow supports specifying a user-assigned managed identity by object ID.Bugs Fixed
DefaultAzureCredentialattempts to authenticate with theMangagedIdentityCredentialand it receives either a failed response that is not json, it will now fall through to the next credential in the chain. #45184AzurePipelinesCredentialso it doesn't result in a redirect response when an invalid system access token is provided.Other Changes
AzureEventSourceListener. Previously, the log level was always set toMicrosoft.Identity.Client.LogLevel.Info.AzurePowerShellCredentialnow utilizes the AsSecureString parameter to Get-AzAccessToken for version 2.17.0 and greater of the Az.Accounts module.AzurePipelinesCredential.v1.12.1Compare Source
1.12.1 (2024-09-26)
Bugs Fixed
AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet (Microsoft.IdentityModel.Protocols.OpenIdConnect)
v8.14.0Compare Source
====
Bug Fixes
ValidationResultinstead ofOperationResultwhen validating a token in a new experimental validation flow. Additionally removed the dependency on Microsoft.IdentityModel.Abstractions. See #3299 for details.v8.13.1Compare Source
====
Dependencies
Microsoft.IdentityModel now depends on Microsoft.Identity.Abstractions 9.3.0
Bug Fixes
Work related to redesign of IdentityModel's token validation logic #2711
v8.13.0Compare Source
====
Fundamentals
CaseSensitiveClaimsIdentity.SecurityTokensetter is now protected internal (was internal). See PR #3278 for details.v8.12.1Compare Source
====
Fundamentals
v8.12.0Compare Source
====
New Features
Added event handling capabilities to the
ConfigurationManager, enabling consumers to subscribe to configuration change events. This enhancement improves extensibility and allows more responsive applications. For details see #3253Bug Fixes
Introduced the expected overload of
Base64UrlEncoder.Decodefor .NET 6 and 8, ensuring compatibility and preventing missing method issues on these frameworks.For details see #3249
Fundamentals
Incorporated AI assist rules to enhance AI agents effectiveness.
For details see #3255
Upgraded analyzer packages for improved diagnostics and code consistency (in particular delegates are added).
For details see #3256
Centralized suppression of RS006 warnings in project files for easier management.
For details see #3230
v8.11.0Compare Source
=====
New Features:
JsonWebTokenHandler.DecryptTokenWithConfigurationAsync, which decrypts a JWE token using keys from eitherTokenValidationParametersor, if not present, from configuration (such as via a ConfigurationManager). This enhancement improves developer experience by enabling asynchronous, cancellation-aware JWE decryption scenarios, aligning with modern .NET async patterns and making integration with external key/configuration sources more robust and observable. See PR #3243 for details.v8.10.0Compare Source
=====
Bug Fixes
Fundamentals
v8.9.0Compare Source
=====
Bug Fixes
New Features
Fundamentals
v8.8.0Compare Source
=====
New Features
Switch.Microsoft.IdentityModel.UpdateConfigAsBlockingswitch. If set, configuration calls will be blocking when metadata is updated, otherwise, if token arrive with a new signing keys, validation errors will be returned to the caller. See PR #3193 for details.Switch.Microsoft.IdentityModel.DoNotScrubExceptionsAppContextSwitch. See PR #3195 and https://aka.ms/identitymodel/app-context-switches for details.System.Thread.Lockobjects for .NET 9 or greater. See PRs #3185 and #3189 for details.v8.7.0Compare Source
=====
Bug Fixes
IsRecoverableExceptionandIsRecoverableExceptionTypewhose signatures were changed in the previous version. See #3181.New Features
Cnfclass public and move it to Microsoft.IdentityModel.Tokens package. See #3165.v8.6.1Compare Source
=====
Bug fix
JsonWebTokenHandlerwhereJwtTokenDecryptionParameters'sAlgandEncwere not set during token decryption, causingIDX10611andIDX10619errors to show null values in the messages. See issue #3003 for details.Fundamentals
v8.6.0Compare Source
=====
New Features
TryAllDecryptionKeysthat let you choose whether to try all decrypt keys when no key matches the token decrypt key IDs. By default it's set to true (legacy behavior) but you can set it to false to avoid tyring all keys which is more performant. See #3128Fundamentals
v8.5.0Compare Source
=====
Reverting previous breaking change
v8.4.0Compare Source
=====
New Features
Repair items
KeyIDshould be present in exception messages and is no longer PII. See #3104 for details.Fundamentals
Work related to redesign of IdentityModel's token validation logic #2711
v8.3.1Compare Source
=====
Bug Fixes
AuthenticationEncryptionProvider.cs. See #3063Fundamentals
Work related to redesign of IdentityModel's token validation logic #2711
v8.3.0Compare Source
=====
New features
Work related to redesign of IdentityModel's token validation logic #2711
Bug fixes
Fundamentals
New Contributors
v8.2.1Compare Source
=====
New features
Bug fixes
Fundamentals
SecurityTokenDescriptor. See 2993.Work related to redesign of IdentityModel's token validation logic #2711
IssuerExtensibility. See 2987.v8.2.0Compare Source
=====
Fundamentals
Work related to redesign of IdentityModel's token validation logic #2711
v8.1.2Compare Source
=====
Bug fixes
CaseSensitiveClaimsIdentityas expected. See 2879Fundamentals
v8.1.1Compare Source
=====
Bug fixes
Configuration
📅 Schedule: Branch creation - "before 07:00 on Thursday" in timezone Europe/Oslo, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.