Repository navigation
Bump Microsoft.NET.Test.Sdk and 2 others - #1457
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Gavin Barron (gavinbarron)
previously approved these changes
Nov 18, 2026
Gavin Barron (gavinbarron)
left a comment
Member
There was a problem hiding this comment.
The updated test SDK and MSTest packages support net8.0, with the MSTest framework and adapter kept at the same version. CI still discovers 119, 9, and 15 tests across the three assemblies and reports successful runs for each. Build and CodeQL also passed.
Gavin Barron (gavinbarron)
enabled auto-merge (squash)
November 18, 2026 00:52
dependabot
Bot
dismissed
Gavin Barron (gavinbarron)’s stale review
via
November 18, 2026 01:04
00fc7e8
dependabot
Bot
force-pushed
the
dependabot/nuget/GraphODataTemplateWriter.Test/mstestframework-29b7897596
branch
from
November 18, 2026 01:04
2224b76 to
00fc7e8
Compare
Bumps Microsoft.NET.Test.Sdk from 17.13.0 to 18.12.0 Bumps MSTest.TestAdapter from 3.8.3 to 4.5.3 Bumps MSTest.TestFramework from 3.8.3 to 4.5.3 --- updated-dependencies: - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.11.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: mstestframework - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.11.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: mstestframework - dependency-name: MSTest.TestAdapter dependency-version: 4.5.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: mstestframework - dependency-name: MSTest.TestFramework dependency-version: 4.5.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: mstestframework ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/nuget/GraphODataTemplateWriter.Test/mstestframework-29b7897596
branch
from
November 18, 2026 01:11
00fc7e8 to
3f1f248
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.
Updated Microsoft.NET.Test.Sdk from 17.13.0 to 18.12.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.12.0
Security fix
This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.12.0
18.11.1
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0.Fixed in:
Microsoft.TestPlatform.CLI18.11.1.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.11.1
18.11.0
What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.10.1...v18.11.0
18.10.2
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.10.0 and 18.10.1.Fixed in:
Microsoft.TestPlatform.CLI18.10.2.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.10.1...v18.10.2
18.10.1
What's Changed
Full Changelog: microsoft/vstest@v18.10.0...v18.10.1
18.10.0
What's Changed
vstest.consoleand datacollector by @nohwnd in Run Microsoft.Testing.Platform test apps under vstest.console and datacollector microsoft/vstest#16201Full Changelog: microsoft/vstest@v18.9.0...v18.10.0
18.9.0
What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.8.0...v18.9.0
18.8.1
What's Changed
Full Changelog: microsoft/vstest@v18.8.0...v18.8.1
18.8.0
What's Changed
Full Changelog: microsoft/vstest@v18.7.0...v18.8.0
18.7.1
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.7.0.Fixed in:
Microsoft.TestPlatform.CLI18.7.1.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.7.0...v18.7.1
18.7.0
What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.6.0...v18.7.0
18.6.0
What's Changed
Changes to tests and infra
... (truncated)
18.5.1
What's Changed
Full Changelog: microsoft/vstest@v18.5.0...v18.5.1
18.5.0
What's Changed
Full Changelog: microsoft/vstest@v18.4.0...v18.5.0
18.4.0
What's Changed
Add LoongArch64 support by @stdmnpkg in Add LoongArch64 support microsoft/vstest#15359
Refactor Condition evaluation by @Youssef1313 in Refactor Condition evaluation microsoft/vstest#15357
Adding info on extensions points part 1 by @nohwnd in Adding info on extensions points part 1 microsoft/vstest#15360
Add option to ask for uploading code QL before the standard window ends by @nohwnd in Add option to ask for uploading code QL before the standard window ends microsoft/vstest#15373
Update runtime versions by @nohwnd in Update runtime versions microsoft/vstest#15372
Fix .NET 10 regression for traits by @Youssef1313 in Fix .NET 10 regression for traits microsoft/vstest#15370
Update target frameworks to net10.0 and net11.0 by @dotnet-maestro[bot] in Update target frameworks to net10.0 and net11.0 microsoft/vstest#15349
Fix names in pipeline matrix so we don't have to align them by @nohwnd in Fix names in pipeline matrix so we don't have to align them microsoft/vstest#15365
Update SECURITY.md by @Youssef1313 in Update SECURITY.md microsoft/vstest#15342
New Contributors
Full Changelog: microsoft/vstest@v18.3.0...v18.4.0
18.3.0
What's Changed
Internal fixes and updates
New Contributors
18.0.2
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.0.0 and 18.0.1.Fixed in:
Microsoft.TestPlatform.CLI18.0.2.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.0.1...v18.0.2
18.0.1
What's Changed
Fixing an issue with loading covrun64.dll on systems that have .NET 10 SDK installed: https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/code-coverage-dynamic-native-instrumentation
Internal changes
Full Changelog: microsoft/vstest@v18.0.0...v18.0.1
18.0.0
What's Changed
Internal fixes and updates
... (truncated)
17.14.2
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI17.14.0 and 17.14.1.Fixed in:
Microsoft.TestPlatform.CLI17.14.2.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v17.14.1...v17.14.2
17.14.1
What's Changed
Full Changelog: microsoft/vstest@v17.14.0...v17.14.1
17.14.0
What'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
... (truncated)
17.14.0-preview-25107-01
What'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
Will probably revert before release:
New Contributors
Full Changelog: microsoft/vstest@v17.13.0...v17.14.0-preview-25107-01
Commits viewable in compare view.
Updated MSTest.TestAdapter from 3.8.3 to 4.5.3.
Release notes
Sourced from MSTest.TestAdapter's releases.
4.5.3
See MSTest 4.5.3 release notes here.
See Microsoft.Testing.Platform (MTP) 2.5.3 release notes here.
4.5.2
See MSTest release notes here.
See Microsoft.Testing.Platform (MTP) release notes here.
4.5.1
See the release notes here
4.5.0
See the release notes here
4.4.1
See the release notes here
4.4.0
See the release notes here
4.3.3
See the release notes here
4.3.2
See the release notes here
4.3.0
See the release notes here
4.2.3
See the release notes here
4.2.2
See the release notes here
4.2.1
See the release notes here
4.1.0
See the release notes here
4.0.2
See the release notes here
4.0.1
See the release notes here
4.0.0
What is new?
Assert.That
MSTest v4 adds a new type of assertion, that allows you to write any expression, and it will inspect the result to give you more information on failure. Providing a very flexible way to assert complicated expressions. Here a simple example:
CallerArgumentExpression
CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages:
CallerArgumentExpression
CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages: