Open
Conversation
cd0f5ea to
2893adf
Compare
a79a7c4 to
1ad0a86
Compare
acde7f0 to
1d9930b
Compare
|
No New Or Fixed Issues Found |
18be2b6 to
1e6618e
Compare
6b62f58 to
9a14bd2
Compare
ebcc4fe to
2dc62fc
Compare
35282de to
319b651
Compare
c0d3837 to
987d03b
Compare
2037afc to
fa28c35
Compare
be5ce15 to
4f97659
Compare
dc3efc5 to
13b24fb
Compare
6d7d4c0 to
0ce13e1
Compare
877e2b0 to
74ca8cd
Compare
74ca8cd to
136bf17
Compare
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.

This PR contains the following updates:
[3.7.2.6]→[3.7.506.4][1.11.4]→[1.17.1][4.5.1]→[4.8.0][4.5.0]→[4.8.0][4.5.0]→[4.8.0][12.19.1]→[12.27.0][3.7.0]→[3.23.0][8.0.11]→[8.0.24][8.0.11]→[8.0.24][8.0.2]→[8.0.24][8.0.2]→[8.0.24][17.10.0]→[17.14.1][2.22.0]→[2.30.0][5.1.0]→[5.3.0][5.1.2]→[5.3.0][8.0.1]→[8.0.3][8.0.1]→[8.0.3][8.0.0]→[8.0.4][1.7.0]→[1.17.5.1][6.0.2]→[6.0.4]8.0.2→8.0.24[2.8.1]→[2.9.2][3.0.2]→[3.1.5]Release Notes
aws/aws-sdk-net (AWSSDK.KeyManagementService)
v3.7.506v3.7.504v3.7.503v3.7.502v3.7.500v3.7.403.1Compare Source
v3.7.403v3.7.402Compare Source
v3.7.401v3.7.400v3.7.304v3.7.303v3.7.302v3.7.301v3.7.300v3.7.200v3.7.104v3.7.103v3.7.102v3.7.101v3.7.4v3.7.3Azure/azure-sdk-for-net (Azure.Identity)
v1.17.1Compare Source
1.17.1 (2025-11-18)
Other Changes
Microsoft.Identity.ClientandMicrosoft.Identity.Client.Extensions.Msaldependencies to version 4.78.0.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 (2025-11-19)
Other Changes
Azure.Identitydependency to version 1.17.1v1.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
v1.12.0Compare Source
1.12.0 (2024-06-17)
Features Added
AzurePipelinesCredentialfor authenticating with Azure Pipelines service connections.OnBehalfOfCredentialnow supports client assertion callbacks for acquiring tokens on behalf of a user.ClientAssertionCredentialOptionsnow supportsTokenCachePersistenceOptionsfor configuring token cache persistence.googleapis/google-cloud-dotnet (Google.Cloud.Kms.V1)
v3.23.0: Google.Cloud.AIPlatform.V1 version 3.23.0Compare Source
Changes in this release:
New features
v3.22.0: Google.Cloud.PubSub.V1 version 3.22.0Compare Source
Changes in this release:
New features
enabledfield for message transforms and adddisabledfield (commit d75a0b0)Documentation improvements
enabledfield for message transforms and adddisabledfield (commit d75a0b0)codein message.google.pubsub.v1.JavaScriptUDFis changed (commit e82746a)v3.21.0: Google.Cloud.PubSub.V1 version 3.21.0Compare Source
Changes in this release:
New features
Documentation improvements
v3.20.0: Google.Cloud.PubSub.V1 version 3.20.0Compare Source
Changes in this release:
New features
v3.19.0: Google.Cloud.PubSub.V1 version 3.19.0Compare Source
Changes in this release:
Bug fixes
New features
v3.18.0: Google.Cloud.BigQuery.Storage.V1 version 3.18.0Compare Source
New features
v3.17.0: Google.Cloud.PubSub.V1 version 3.17.0Compare Source
Changes in this release:
New features
Documentation improvements
v3.16.0: Google.Cloud.PubSub.V1 version 3.16.0Compare Source
Changes in this release:
New features
v3.15.0: Google.Cloud.PubSub.V1 version 3.15.0Compare Source
Changes in this release:
New features
v3.14.0: Google.Cloud.PubSub.V1 version 3.14.0Compare Source
Changes in this release:
Bug fixes
New features
The last two of these features can cause user-visible changes. In particular:
All of these changes should be "net positive", but if they cause any issues, please file a bug.
v3.13.0: Google.Cloud.Firestore version 3.13.0Compare Source
New features
v3.12.0: Google.Cloud.PubSub.V1 version 3.12.0Compare Source
Changes in this release:
New features
v3.11.0: Google.Cloud.Firestore version 3.11.0Compare Source
New features
v3.10.0: Google.Cloud.Kms.V1 version 3.10.0Compare Source
Changes in this release:
New features
v3.9.0: Google.Cloud.BigQuery.V2 version 3.9.0Compare Source
Changes in this release:
New features
v3.8.0: Google.Cloud.Kms.V1 version 3.8.0Compare Source
Changes in this release:
Documentation improvements
dotnet/dotnet (Microsoft.EntityFrameworkCore.Design)
v8.0.18: .NET 8.0.18You can build .NET 8.0 from the repository by cloning the release tag
v8.0.18and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v8.0.17: .NET 8.0.17You can build .NET 8.0 from the repository by cloning the release tag
v8.0.17and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v8.0.16: .NET 8.0.16You can build .NET 8.0 from the repository by cloning the release tag
v8.0.16and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v8.0.15: .NET 8.0.15You can build .NET 8.0 from the repository by cloning the release tag
v8.0.15and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v8.0.14: .NET 8.0.14You can build .NET 8.0 from the repository by cloning the release tag
v8.0.14and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v8.0.13: .NET 8.0.13You can build .NET 8.0 from the repository by cloning the release tag
v8.0.13and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v8.0.12: .NET 8.0.12You can build .NET 8.0 from the repository by cloning the release tag
v8.0.12and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
microsoft/vstest (Microsoft.NET.Test.Sdk)
v17.14.1What's Changed
47eb51bFull Changelog: microsoft/vstest@v17.14.0...v17.14.1
v17.14.0What's Changed
.NET versions updated
This version of VS Test upgraded .NET to net8 and net9. All projects targeting net6.0 (or other end-of-life .NET target frameworks) should pin their version of Microsoft.NET.Test.SDK to 17.13.0, or update the projects to net8 or newer. We remain backwards compatible with previous versions of Microsoft.NET.Test.SDK. This change does NOT prevent you from:
It also has no impact on .NET Framework projects, where we continue targeting .NET Framework 4.6.2.
Changes
Internal version updates and fixes
New Contributors
Full Changelog: microsoft/vstest@v17.13.0...v17.14.0
v17.13.0What's Changed
Add letter number among valid identifiers in class name by @nohwnd in #13868
Fix formatting in Runner by @mthalman in #13871
Downgrade xunit skip warning to info by @nohwnd in #10381
Add msdia for arm64 into nuget by @nohwnd in #10382
Enable native debugging for vstest.console by @ocitrev in #10401
Fix RFCs links by @Youssef1313 in #10424
Convert to auto property by @nohwnd in #10365
Update Versions.props by @nohwnd in #10378
Enable TSA by @jakubch1 in #10385
Arm64 dia by @nohwnd in #10390
Update source-build team references by @MichaelSimons in #10388
Exclude .signature.p7s from nupkg file count by @ellahathaway in #10418
Set NetCurrent so that it doesn't roll forward automatically by @ViktorHofer in #10622
New Contributors
Full Changelog: microsoft/vstest@v17.12.0...v17.13.0
v17.12.0What's Changed
Internal and infrastructure fixes:
Full Changelog: microsoft/vstest@v17.11.1...v17.12.0
v17.11.1What's Changed
Full Changelog: microsoft/vstest@v17.11.0...v17.11.1
v17.11.0What'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.