Update nuget packages (major)#72
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
00644f4 to
5560ac3
Compare
5560ac3 to
9817e91
Compare
01c7ae2 to
78b172a
Compare
b1a7630 to
7899e02
Compare
7899e02 to
a84fecc
Compare
29371a0 to
fe31847
Compare
e64553a to
1ff91aa
Compare
1ff91aa to
d912947
Compare
9402f98 to
9fe34c0
Compare
9fe34c0 to
f7e1c80
Compare
1a4049c to
2823545
Compare
2823545 to
f10fc42
Compare
79c21ef to
b950ac5
Compare
b950ac5 to
26f153e
Compare
f5acfbe to
aa7841f
Compare
459122a to
c266d9d
Compare
f924128 to
78ed952
Compare
65e7326 to
6c8c306
Compare
6c8c306 to
521487f
Compare
7af386e to
83f280c
Compare
97fbf75 to
b605774
Compare
8bb8d01 to
07720b7
Compare
07720b7 to
468fa47
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.11.0→5.3.04.14.0→5.3.04.13.0→5.3.04.14.0→5.3.04.13.0→5.3.04.14.0→5.3.04.14.0→5.3.017.13.0→18.5.13.13.3→4.6.03.6.1→4.13.05.2.0→6.2.07.0.0→10.0.86.0.4→10.0.06.0.0→10.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
microsoft/vstest (Microsoft.NET.Test.Sdk)
v18.5.1What's Changed
Full Changelog: microsoft/vstest@v18.5.0...v18.5.1
v18.5.0What's Changed
Full Changelog: microsoft/vstest@v18.4.0...v18.5.0
v18.4.0What's Changed
Add LoongArch64 support by @stdmnpkg in #15359
Refactor Condition evaluation by @Youssef1313 in #15357
Adding info on extensions points part 1 by @nohwnd in #15360
Add option to ask for uploading code QL before the standard window ends by @nohwnd in #15373
Update runtime versions by @nohwnd in #15372
Fix .NET 10 regression for traits by @Youssef1313 in #15370
Update target frameworks to net10.0 and net11.0 by @dotnet-maestro[bot] in #15349
Fix names in pipeline matrix so we don't have to align them by @nohwnd in #15365
Update SECURITY.md by @Youssef1313 in #15342
New Contributors
Full Changelog: microsoft/vstest@v18.3.0...v18.4.0
v18.3.0What's Changed
Internal fixes and updates
New Contributors
v18.0.1What'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
v18.0.0What's Changed
Internal fixes and updates
New Contributors
Full Changelog: microsoft/vstest@v17.14.1...v18.0.0
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
nunit/nunit (NUnit)
v4.6.0: NUnit 4.6.0Compare Source
See release notes for details.
v4.5.1: V 4.5.1Compare Source
See release notes for details.
v4.5.0: V 4.5.0Compare Source
See release notes for details.
v4.4.0: NUnit 4.4.0Compare Source
See release notes for details.
v4.3.2: NUnit 4.3.2Compare Source
This is a hotfix release.
See release notes for details.
v4.3.1: NUnit 4.3.1Compare Source
This is a hotfix release.
See release notes for details.
v4.3.0: NUnit 4.3.0Compare Source
See release notes
v4.2.2: NUnit 4.2.2Compare Source
Hotfix for fixing regression bug #4802
What's Changed
Full Changelog: nunit/nunit@4.2.1...4.2.2
v4.2.1: NUnit 4.2.1Compare Source
Hotfix release for Issue #4794 and #4795, affecting .Net Framework.
v4.2.0: NUnit 4.2.0Compare Source
See release notes
v4.1.0: NUnit 4.1.0See release notes
v4.0.1: NUnit 4.0.1Patch release to fix windows targets
See release notes
and
See migration guide
v4.0.0All changes, see release notes
v3.14.0: NUnit 3.14.0See release notes
nunit/nunit.analyzers (NUnit.Analyzers)
v4.13.0: NUnit Analyzers 4.13 - May 2, 2026Compare Source
NUnit Analyzers 4.13 - May 2, 2026
This release of the NUnit Analyzers updates analyzer handling for the NUnit 4.6 API change that replaces
ActualValueDelegate<>withFunc<>- see nunit/nunit#4824 for more information.Analyzers now also consider the return type of
Func<>in assertions. The release also includes one bug fix andsome dependency updates.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Func<T>return valuesBugs
Tooling, Process, and Documentation
v4.12.0: NUnit Analyzers 4.12 - March 3, 2026Compare Source
NUnit Analyzers 4.12 - March 3, 2026
This release of the NUnit Analyzers improves
NUnit1029to account forTestCaseSourcesupport for params and optional arguments. It also introduces a new analyzer for incorrect
usage of
Is.Not.Null.Or.Empty, fixes regressions inNUnit2005andNUnit2055, and updatesNUnit package dependencies.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Is.Not.Null.Or.EmptyusedBugs
NUnit2055can generate invalid code for classic assertsNUnit2005tries to useIs.Emptyconstraint on incompatible types.Tooling, Process, and Documentation
v4.11.2: NUnit Analyzers 4.11.2 - November 2, 2025Compare Source
NUnit Analyzers 4.11.2 - November 2, 2025
This release of the NUnit Analyzers fixes a problem in the
NUnit2057analyzer for unnecessary use of lambdaexpressions. The release also extends
NUnit2021so that it can determining ifIs.NaNorIs.Not.NaNconstraintsare used on incompatible types.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
v4.11.1Compare Source
This release of the NUnit Analyzers fixes a regression related to the analysis of nullable enum parameters in
NUnit1001andNUnit1031. The release also contains a new analyzer and codefix for unnecessary usage of lambdaexpressions in asserts.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
v4.11.0: NUnit Analyzers 4.11 - October 28, 2025Compare Source
NUnit Analyzers 4.11 - October 28, 2025
This release of the NUnit Analyzers includes improvements and fixes related to
IDisposablehandling and initializationin
SetUpandOneTimeSetUpmethods. It also introduces the ability to configure additional methods that should betreated as
SetUpandTearDownmethods by the analyzers. This can be done in the.editorconfig, and there are fourconfigurations for this:
dotnet_diagnostic.NUnit.additional_setup_methodsdotnet_diagnostic.NUnit.additional_teardown_methodsdotnet_diagnostic.NUnit.additional_one_time_setup_methodsdotnet_diagnostic.NUnit.additional_one_time_teardown_methodsEach configuration accepts a list of method names, separated by commas, semicolons, or spaces. For example:
dotnet_diagnostic.NUnit.additional_setup_methods = CustomSetup, MyInitAs in recent releases, a major part of this work was contributed by @manfred-brands.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v4.10.0: NUnit Analyzers 4.10 - August 9, 2025Compare Source
NUnit Analyzers 4.10 - August 9, 2025
This release of the NUnit Analyzers contains some minor improvements to NUnit2050, NUnit2056, and NUnit2007 as well
as some improvements to existing tests. Once again, @manfred-brands was responsible for the majority of the work.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Bugs
Tooling, Process, and Documentation
v4.9.2Compare Source
This release of the NUnit Analyzers extends the
NUnit3001nullability suppressorto also work in the context of
Assert.EnterMultipleScopeand other using statements.The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
v4.9.1Compare Source
This release of the NUnit Analyzers fixes a problem with the code-fix for translating
Assert.Multiple/Assert.MultipleAsyncinto the newAssert.EnterMultipleScopeformatwhen 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
v4.9.0: NUnit Analyzers 4.9 - June 11, 2025Compare Source
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.MultipleAsyncinto the newAssert.EnterMultipleScopeformat, as wellas for converting
is Tchecks 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
NUnit4002shouldn't trigger forTvsnullable<T>struct typesTooling, Process, and Documentation
v4.8.1Compare Source
This release of the NUnit Analyzers fixes a problem with
NUnit4002when applied to comparisons between non-numbertypes - e.g. strings.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Bugs
v4.8.0: NUnit Analyzers 4.8 - May 22, 2025Compare Source
NUnit Analyzers 4.8 - May 22, 2025
This release of the NUnit Analyzers adds a new diagnostic
NUnit1034that checkswhether base TestFixtures are declared as
abstract. When a base class is notabstractit will also be run as a standalone test which is most times not the intention.
The release also contains some fixes to
NUnit4002andNunit2045.The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v4.7.0: NUnit Analyzers 4.7 - April 1, 2025Compare Source
NUnit Analyzers 4.7 - April 1, 2025
The release primarily add another diagnostic
NUnit4002- and associated codefix - to help simplifyEqualToconstraints 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
Configuration
📅 Schedule: (UTC)
🚦 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.