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:
[3.7.400.53]->[3.7.502.3][1.13.1]->[1.17.0][4.7.0]->[4.8.0][4.7.0]->[4.8.0][4.7.0]->[4.8.0][12.23.0]->[12.26.0][3.15.0]->[3.19.0][9.0.0]->[9.0.10][9.0.0]->[9.0.10][9.0.0]->[9.0.10][9.0.0]->[9.0.10][3.0.0]->[3.5.0][9.0.1]->[9.0.4][5.2.0]->[5.3.0]Release Notes
aws/aws-sdk-net (AWSSDK.KeyManagementService)
v3.7.502v3.7.500v3.7.403.1Compare Source
v3.7.403v3.7.402Compare Source
v3.7.401Azure/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)googleapis/google-cloud-dotnet (Google.Cloud.Kms.V1)
v3.19.0: Google.Cloud.Kms.V1 version 3.19.0Compare Source
New features
v3.18.0: Google.Cloud.Kms.V1 version 3.18.0Compare Source
Documentation improvements
DESTROYEDin enumCryptoKeyVersionStateis changedv3.17.0: Google.Cloud.Kms.V1 version 3.17.0Compare Source
New features
Documentation improvements
v3.16.0: Google.Cloud.Kms.V1 version 3.16.0Compare Source
Changes in this release:
New features
Documentation improvements
CryptoKeyVersionAlgorithmis changed (commit d7e6cd5)dotnet/efcore (Microsoft.EntityFrameworkCore.Design)
v9.0.10: .NET 9.0.10Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.9...v9.0.10
v9.0.9: .NET 9.0.9Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.8...v9.0.9
v9.0.8v9.0.7: .NET 9.0.7Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.6...v9.0.7
v9.0.6Bug Fixes
The translation of
FullTextScorein Cosmos Full-Text Search has been updated to use multiple keywords instead of a keyword array, addressing issues with search accuracy and query compatibility. This resolves #35983 and ensures more reliable full-text search results.#36000 by @maumar
Dependency Updates
Updated the Arcade build infrastructure dependencies for the 8.0 release branch, bringing in the latest improvements and security fixes from the Arcade ecosystem.
#35930 by @dotnet-maestro
Updated Arcade dependencies for the 9.0 release branch, ensuring the build system benefits from the latest tooling and reliability enhancements.
#36006 by @dotnet-maestro
Another update to Arcade dependencies for the 8.0 branch, further aligning with upstream improvements and fixes.
#36085 by @dotnet-maestro
Additional update to Arcade dependencies for the 9.0 branch, maintaining up-to-date build tooling and infrastructure.
#36065 by @dotnet-maestro
Technical Improvements
Integrated various internal commits into the 8.0 release branch, improving code quality, maintainability, and aligning with internal standards.
#35926 by @vseanreesermsft
Additional internal commits merged into the 8.0 branch, further enhancing stability and maintainability.
#36080 by @vseanreesermsft
Integrated internal improvements into the 9.0 branch, ensuring consistency and codebase health.
#36081 by @vseanreesermsft
Infrastructure
Updated the product branding and version numbers to 9.0.6, ensuring that all assemblies and packages reflect the correct release version.
#36044 by @vseanreesermsft
Updated branding for the 8.0 release line to version 8.0.17, keeping versioning consistent across all release artifacts.
#36043 by @vseanreesermsft
Miscellaneous
Automated merge of changes from the 8.0 branch into the 9.0 branch, ensuring that all relevant fixes and improvements are carried forward.
#35927 by @github-actions
Merged the 9.0 branch into the 9.0-staging branch, preparing for further testing and validation before final release.
#36051 by @AndriySvyryd
Another automated merge from 8.0 to 9.0, keeping branches synchronized.
#36088 by @github-actions
Merged changes from the 9.0-staging branch back into the main 9.0 branch, finalizing updates for this release.
#36089 by @AndriySvyryd
This summary is generated and may contain inaccuracies. For complete details, please review the linked pull requests.
Full Changelog: v9.0.5...v9.0.6
v9.0.5: .NET 9.0.5Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.4...v9.0.5
v9.0.4: .NET 9.0.4Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.3...v9.0.4
v9.0.3: .NET 9.0.3Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.2...v9.0.3
v9.0.2: .NET 9.0.2Release
What's Changed
Full Changelog: dotnet/efcore@v9.0.1...v9.0.2
v9.0.1: .NET 9.0.1Release
What's Changed
Configuration
📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), 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.