Bump Microsoft.NET.Test.Sdk and NUnit.Analyzers #3675
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 17.14.1.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
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 NUnit.Analyzers from 4.6.0 to 4.9.2.
Release notes
Sourced from NUnit.Analyzers's releases.
4.9.2
NUnit Analyzers 4.9.2 - June 17, 2025
This release of the NUnit Analyzers extends the
NUnit3001
nullability suppressorto also work in the context of
Assert.EnterMultipleScope
and other using statements.The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
4.9.1
NUnit Analyzers 4.9.1 - June 12, 2025
This release of the NUnit Analyzers fixes a problem with the code-fix for translating
Assert.Multiple
/Assert.MultipleAsync
into the newAssert.EnterMultipleScope
formatwhen the test method already is asynchronous and have a return type different from
Task
.The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Bugs
4.9.0
NUnit Analyzers 4.9 - June 11, 2025
This release of the NUnit Analyzers adds several new analyzers. For the
RangeAttribute
,the analyzers now warn about potential issues at runtime.
It also introduces an analyzer and code fix for translating
Assert.Multiple
/Assert.MultipleAsync
into the newAssert.EnterMultipleScope
format, as wellas for converting
is T
checks intoIs.InstanceOf<T>()
constraints.For
NUnit2021
, the analyzer now respectsUsingPropertiesComparer
, including enhancementsthat will be available in NUnit 4.4.
Finally, this release includes improvements to
NUnit2007
,NUnit2045
, andNUnit4002
.See the list of resolved issues below for more details.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
NUnit4002
shouldn't trigger forT
vsnullable<T>
struct typesTooling, Process, and Documentation
4.8.1
NUnit Analyzers 4.8.1 - May 29, 2025
This release of the NUnit Analyzers fixes a problem with
NUnit4002
when applied to comparisons between non-numbertypes - e.g. strings.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Bugs
4.8.0
NUnit Analyzers 4.8 - May 22, 2025
This release of the NUnit Analyzers adds a new diagnostic
NUnit1034
that checkswhether base TestFixtures are declared as
abstract
. When a base class is notabstract
it will also be run as a standalone test which is most times not the intention.
The release also contains some fixes to
NUnit4002
andNunit2045
.The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
4.7.0
NUnit Analyzers 4.7 - April 1, 2025
The release primarily add another diagnostic
NUnit4002
- and associated codefix - to help simplifyEqualTo
constraints when the expected value is a simple constant - e.g.true
,false
,0
, ordefault
. The release also removes some false positives forNunit1029
.As tooling contributions the analyzers now build using .NET8.0 and also analyzers and codefixes are
now split into separate projects as only editors should load codefixes.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version
will 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 version
will 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