Skip to content

Bump coverlet.collector and 4 others #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
brych126 merged 1 commit into from
Aug 3, 2025
Merged

Bump coverlet.collector and 4 others #3

brych126 merged 1 commit into from
Aug 3, 2025

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 3, 2025

Updated coverlet.collector from 6.0.0 to 6.0.4.

Release notes

Sourced from coverlet.collector's releases.

6.0.4

Fixed

  • Fix empty coverage report when using include and exclude filters #​1726

Diff between 6.0.3 and 6.0.4

6.0.3

Fixed

Improvements

  • Cache the regex used in InstrumentationHelper #​1693
  • Enable dotnetTool integration tests for linux #​660

Diff between 6.0.2 and 6.0.3

6.0.2

Fixed

  • Threshold-stat triggers error #​1634
  • Fixed coverlet collector 6.0.1 requires dotnet sdk 8 #​1625
  • Type initializer errors after updating from 6.0.0 to 6.0.1 #​1629
  • Exception when multiple exclude-by-attribute filters specified #​1624

Improvements

  • More concise options to specify multiple parameters in coverlet.console #​1624

Diff between 6.0.1 and 6.0.2

6.0.1

Fixed

  • Uncovered lines in .NET 8 for inheriting records #​1555
  • Fix record constructors not covered when SkipAutoProps is true #​1561
  • Fix .NET 7 Method Group branch coverage issue #​1447
  • Fix ExcludeFromCodeCoverage does not exclude method in a partial class #​1548
  • Fix ExcludeFromCodeCoverage does not exclude F# task #​1547
  • Fix issues where ExcludeFromCodeCoverage ignored #​1431
  • Fix issues with ExcludeFromCodeCoverage attribute #​1484
  • Fix broken links in documentation #​1514
  • Fix problem with coverage for .net5 WPF application #​1221 by https://github.com/lg2de
  • Fix unable to instrument module for Microsoft.AspNetCore.Mvc.Razor #​1459 by https://github.com/lg2de

Improvements

Diff between 6.0.0 and 6.0.1

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 17.6.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:

  • Updating to the latest VS, and running tests from net6.0 test projects.
  • Updating to the latest .NET SDK, and running tests from net6.0 test projects.

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

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:

  • Updating to the latest VS, and running tests from net6.0 test projects.
  • Updating to the latest .NET SDK, and running tests from net6.0 test projects.

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

17.13.0

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.12.0...v17.13.0

17.12.0

What's Changed

Internal and infrastructure fixes:

Full Changelog: microsoft/vstest@v17.11.1...v17.12.0

17.11.1

What's Changed

Full Changelog: microsoft/vstest@v17.11.0...v17.11.1

17.11.0

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.10.0...v17.11.0-release-24352-06

17.11.0-release-24373-02

What's Changed

Full Changelog: microsoft/vstest@v17.11.0-release-24352-06...v17.11.0-release-24373-02

17.11.0-release-24352-06

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.10.0...v17.11.0-release-24352-06

17.10.0

What's Changed

And many infrastructure related changes and updates.

New Contributors

Full Changelog: microsoft/vstest@v17.9.0...v17.10.0

17.10.0-release-24177-07

What's Changed

New Contributors

And many infrastructure related changes to migrate our pipelines to common build system.

Full Changelog: microsoft/vstest@v17.10.0-preview-24080-01...v17.10.0-release-24177-07

17.10.0-preview-24080-01

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.9.0-preview-23577-04...v17.10.0-preview-24080-01

17.9.0

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.8.0...v17.9.0

17.9.0-release-23619-01

What's Changed

Full Changelog: microsoft/vstest@v17.9.0-preview-23577-04...v17.9.0-release-23619-01

17.9.0-preview-23577-04

What's Changed

  • Updated VSSDK.BuildTools version by @​cvpoienaru in #​4765
  • Update dump client to latest by @​nohwnd in #​4724
  • Fix staircase in logger by @​nohwnd in #​4756
  • Create a proper MSBuild ToolTask based VSTestTask by @​nohwnd in #​2702
  • Fix CPU is consumed by polling frequently when there is no subscriber by @​nohwnd, @​cvpoienaru in #​4735
  • Remove javascript in HtmlLogger by @​daveMueller in #​4744
  • Update VSIX metadata by @​nohwnd in #​4550
  • Add platform guard by @​dotMorten in #​4737

Full Changelog: microsoft/vstest@v17.9.0-preview-23531-01...v17.9.0-preview-23577-04

17.9.0-preview-23531-01

What's Changed

Full Changelog: microsoft/vstest@v17.9.0-preview-23503-02...v17.9.0-preview-23531-01

17.9.0-preview-23503-02

What's Changed

  • Remove dependency on Nuget.Frameworks by @​nohwnd in #​4693

Full Changelog: microsoft/vstest@v17.8.0-release-23468-02...v17.9.0-preview-23503-02

17.8.0

What's Changed

Full Changelog: microsoft/vstest@v17.7.2...v17.8.0

17.8.0-release-23468-02

What's Changed

  • Upgrade Newtonsoft.Json from 13.0.1 to 13.0.3 by @​mthalman in #​4681

Full Changelog: microsoft/vstest@v17.8.0-preview-23424-02...v17.8.0-release-23468-02

17.8.0-preview-23424-02

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.8.0-preview-23371-04...v17.8.0-preview-23424-02

17.8.0-preview-23371-04

Issues Fixed

  • Take System dlls from testhost folder #​4610
  • Simplify naming in ExecutionTests
  • Fix XmlException when writing Html log with certain test names #​4576

Full Changelog: here

Drops

17.7.2

What's Changed

Full Changelog: microsoft/vstest@v17.7.1...v17.7.2

17.7.1

What's Changed

  • Take System dlls from testhost folder to fix running .NET Framework dlls on mono and under VS on Mac in #​4610 by @​Evangelink
  • Fix hangs in parallel execution and discovery in #​4629 by @​nohwnd
  • Fix executable bitness for testhost.x86 in #​4654 by @​nohwnd

Full Changelog: microsoft/vstest@v17.7.0...v17.7.1

17.7.0

⚠️ Microsoft.TestPlatform 17.7.0 nuget package is hidden from Nuget.org, we've encountered an unexpected issue with versioning which prevents it from being used in all AzDO clients. We are working on a fix.

The most pressing issues were all backported to 17.6.1, 17.6.2 and 17.6.3.

Issues fixed (since 17.6.3)

  • Don't print socket transport error in console by @​nohwnd in #​4493 which fixes #​4461
    When testhost crashes, we no longer print the transport error:

     ---> System.Exception: Unable to read data from the transport connection: 
 		An existing connection was forcibly closed by the remote host..

    This error is a side-effect or our architecture is almost never the culprit. Instead it leads developers away from the actual issue which is crash of testhost, or datacollector.

  • Pass workloads to proxy managers in #​4422 by @​nohwnd
    Which allows datacollector users to only receive the sources that are currently running in the testhost associated to datacollector, instead of all the sources that have the same target framework.

  • Fix Newtonsoft versions in testhost.deps.json in #​4367 by @​nohwnd
    testhost.runtimeconfig.json files that we ship with testhost contained an old version of Newtonsoft.Json. The version in this file does not have an effect on execution, but some compliance tools statically analyze it and report possible vulnerabilities.

Other fixes:

  • Replacing calls to BuildMultipleAssemblyPath when passing only one source in acceptance tests in #​4358 by @​daveMueller
  • Check for null Path in #​4391 by @​lewing
  • Remove unused variable in #​4425 by @​mthalman
  • Fix execution gets stucks on single netstandard source by @​nohwnd in #​4497 which fixes #​4392
  • TestObject use ConcurrentDictionary instead of Dictionary in #​4450 by @​Evangelink
  • Drop usage of Microsoft.Internal.TestPlatform.Remote in #​4456 by @​Evangelink

Special thanks to @​SimonCropp for the many fixes regarding nullability spelling and code style in #​4518, #​4520, #​4525, #​4526, #​4521, #​4519, #​4522, #​4529 🙇

Full Changelog: microsoft/vstest@v17.6.3...v17.7.0

Drops

  • Microsoft.TestPlatform.ObjectModel : v17.7.0

17.7.0-preview-23364-03

Issues Fixed

  • Trim away netframework targets in source-build #​4357
  • Re-enable publishing nugets, don't continue on error #​4356
  • Merged PR 30352: arcade into main
  • Merged PR 29591: Onboard to arcade

Full Changelog: here

Drops

17.7.0-preview.23280.1

⚠️ This version of Microsoft.TestPlatform nuget was unlisted on Nuget.org, because it causes issues when running tests in AzureDevOps, when VSTest installer is used, and configured to pick up the latest preview version (#​4544).


What is new since 17.6.0?

Version 17.7.0 was filled with moving our infrastructure to build via Arcade, which brought us a more unified build experience and better cooperation with other teams in dotnet organization.

This migration brought a major change to our versioning of preview packages, which will no longer follow the 17.6.0-preview-20230223-05 (<version>-preview<date>-<build>).

Fixes

When test run aborts we are no longer printing the connection related error:

System.Exception: One or more errors occurred.
 ---> System.Exception: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
 ---> System.Exception: An existing connection was forcibly closed by the remote host.
   at System.Net.Sockets.NetworkStream.Read(Span`1 buffer)

This error is a common source of confusion, and is not actionable for the user. It simply means that testhost crashed, and the testhost error follows after it, or that logs need to be inspected.

When both --blame-hang and --blame-crash are specified on Windows, and hang dump is triggered then stopping ProcDump is subject to a race condition. Stopping ProcDump too early causes testhost to crash and no dump (nor the hang dump or the crash dump) is generated. This release fixes this issue by waiting for crash dump to finish.

Regressions from 17.5.0 causing crashes of TestHost when .NET Standard dlls, or TestPlatform own dlls are provided for run are fixed, and a list of dlls that are known platform dlls are excluded.

Data collectors consuming the dlls that are run are now provided only paths to dlls that the current testhost is running, rather than all dlls that were provided to the run.

Additional fixes

New Contributors

... (truncated)

17.6.3

Issues Fixed

  • [rel/17.6] Update version to 17.6.3 by @​nohwnd in #​4555
  • [rel/17.6] Disable pre-start of testhosts by @​nohwnd in #​4554

Full Changelog: microsoft/vstest@v17.6.2...v17.6.3

Artifacts

  • TestPlatform vsix: 17.6.3
  • Microsoft.TestPlatform.ObjectModel : 17.6.3

17.6.2

Fixes

This patch addresses the problems that were introduced in 17.6.0 that happen when running on AzDo with the default test.dll filter, which includes additional TestPlatform dlls into the run and fails it.

To mitigate this issue we solved the bug in 17.6.1, and added additional exclusions for known assemblies that are coming from TestPlatform and commonly used test adapters, to avoid trying to run tests from those assemblies.

Description and workarounds for this issue are available here: microsoft/vstest#4516

Full Changelog: microsoft/vstest@v17.6.1...v17.6.2

Artifacts
TestPlatform vsix: 17.6.2
Microsoft.TestPlatform.ObjectModel : 17.6.2

17.6.1

Issues Fixed

This is a tiny patch to fixup few latest issues,

Internal updates:

Full Changelog: microsoft/vstest@v17.6.0...v17.6.1

Artifacts

  • TestPlatform vsix: 17.6.1
  • Microsoft.TestPlatform.ObjectModel : 17.6.1

Commits viewable in compare view.

Updated NUnit from 3.13.3 to 4.3.2.

Release notes

Sourced from NUnit's releases.

4.3.2

This is a hotfix release.
See release notes for details.

4.3.1

This is a hotfix release.
See release notes for details.

4.3.0

See release notes

4.2.2

Hotfix for fixing regression bug #​4802

What's Changed

Full Changelog: nunit/nunit@4.2.1...4.2.2

4.2.1

Hotfix release for Issue #​4794 and #​4795, affecting .Net Framework.

4.2.0

See release notes

4.1.0

See release notes

4.0.1

Patch release to fix windows targets

See release notes
and
See migration guide

4.0.0

See release notes
and
See migration guide

4.0.0-beta.1

See release notes
and information

3.14.0

See release notes

Commits viewable in compare view.

Updated NUnit.Analyzers from 3.6.1 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 suppressor
to also work in the context of Assert.EnterMultipleScope and other using statements.

The release contains contributions from the following users (in alphabetical order):

  • @​artificialWave
  • @​manfred-brands
  • @​mikkelbu

Issues Resolved

Features and Enhancements

  • #​892 Assert.EnterMultipleScope not detecting nullability properly

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 new Assert.EnterMultipleScope format
when 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):

  • @​MaceWindu
  • @​manfred-brands
  • @​mikkelbu

Issues Resolved

Bugs

  • #​888 Assert.MultipleAsync -> EnterMultipleScope autofix produce invalid code

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 new Assert.EnterMultipleScope format, as well
as for converting is T checks into Is.InstanceOf<T>() constraints.

For NUnit2021, the analyzer now respects UsingPropertiesComparer, including enhancements
that will be available in NUnit 4.4.

Finally, this release includes improvements to NUnit2007, NUnit2045, and NUnit4002.
See the list of resolved issues below for more details.

The release contains contributions from the following users (in alphabetical order):

  • @​MaceWindu
  • @​manfred-brands
  • @​mikkelbu
  • @​OsirisTerje
  • @​stevenaw

Issues Resolved

Features and Enhancements

  • #​880 NUnit2007 could flag typeof() as a constant first parameter
  • #​866 When Assert.Multiple is found, should suggest to convert to Assert.EnterMultipleScope
  • #​865 NUnit 2045 suggest Assert.Multiple, but should suggest Assert.EnterMultipleScope
  • #​857 NUnit2021 Should not raise for UsingPropertiesComparer
  • #​765 Add Rule for converting is T into Is.InstanceOf()
  • #​89 Test the correct usage of the Range attribute

Bugs

  • #​879 NUnit4002 shouldn't trigger for T vs nullable<T> struct types

Tooling, Process, and Documentation

  • #​868 chore: bump version

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-number
types - e.g. strings.

The release contains contributions from the following users (in alphabetical order):

  • @​adrianbanks
  • @​manfred-brands
  • @​mikkelbu

Issues Resolved

Bugs

  • #​870 Compilation error caused by exception in an analyzer after updating to v4.8.0

4.8.0

NUnit Analyzers 4.8 - May 22, 2025

This release of the NUnit Analyzers adds a new diagnostic NUnit1034 that checks
whether base TestFixtures are declared as abstract. When a base class is not abstract
it will also be run as a standalone test which is most times not the intention.

The release also contains some fixes to NUnit4002 and Nunit2045.

The release contains contributions from the following users (in alphabetical order):

  • @​Bartleby2718
  • @​CharliePoole
  • @​MaceWindu
  • @​manfred-brands
  • @​mikkelbu
  • @​Rabadash8820

Issues Resolved

Features and Enhancements

  • #​840 Detect incorrect or questionable use of TestFixture inheritance.

Bugs

  • #​862 NUnit.Analyzers doesn't recognize the version of NUnit in use
  • #​856 NUnit4002 shouldn't trigger for unknown types

Tooling, Process, and Documentation

  • #​861 Add missing backticks in NUnit4002.md
  • #​855 chore: bump version

4.7.0

NUnit Analyzers 4.7 - April 1, 2025

The release primarily add another diagnostic NUnit4002 - and associated codefix - to help simplify
EqualTo constraints when the expected value is a simple constant - e.g. true, false, 0, or
default. The release also removes some false positives for Nunit1029.

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):

  • @​cbersch
  • @​Dreamescaper
  • @​manfred-brands
  • @​mikkelbu
  • @​seanblue
  • @​zlepper

Issues Resolved

Features and Enhancements

  • #​828 Replace Is.EqualTo(default) with Is.Default
  • #​826 Suggest to use Is.Null instead of Is.EqualTo(null)
  • #​824 Use Is.False / Is.True instead of Is.EqualTo

Bugs

  • #​832 False positive for Nunit1029 when only a type argument is use

Tooling, Process, and Documentation

  • #​853 chore: Add NUnit4002.md solution file
  • #​846 chore: Bump NUnit3TestAdapter to version 5
  • #​843 chore(deps): Bump Microsoft.NET.Test.Sdk and Microsoft.NETFramework.ReferenceAssemblies
  • #​838 chore: bump version
  • #​677 Build using .NET8.0 SDK

4.6.0

NUnit Analyzers 4.6 - January 9, 2025

This release contains two improvements: Allowing NUnit1001 to understand DateOnly and TimeOnly parameters in
TestCaseUsage and making NUnit2045 support Assert.EnterMultipleScope (introduced in NUnit version 4.2).

The release contains contributions from the following users (in alphabetical order):

  • @​Dreamescaper
  • @​manfred-brands
  • @​mikkelbu

Issues Resolved

Features and Enhancements

  • #​820 NUnit1001 compains about DateOnly parameters
  • #​769 Recognized the new Assert.EnterMultipleScope() concept.

Tooling, Process, and Documentation

  • #​829 chore: Bump year to 2025 in copyrights
  • #​823 chore: Bump cake.tool to version 4
  • #​822 chore: Bump NUnit to 4.3.2
  • #​818 chore: Replace "buildstats.info" with "img.shields.io"
  • #​815 chore: bump version

4.5.0

NUnit Analyzers 4.5 - December 22, 2024

The release primarily fixes a problem with the NUnit Analyzers when used with NUnit 4.3.1 - see #​811 for more
information. In additional, we have also added some smaller improvements and bug fixes.

The release contains contributions from the following users (in alphabetical order):

  • @​manfred-brands
  • @​mikkelbu
  • @​RenderMichael
  • @​zlepper

Issues Resolved

Features and Enhancements

  • #​811 NUnit2021 ignores cast operation since NUnit 4.3.1
  • #​801 Allow NUnit2005 to recognize Is.Empty

Bugs

  • #​794 AD0001: Occasional InvalidOperationException error in analyzer in IDE

Tooling, Process, and Documentation

  • #​808 chore: Correct typo
  • #​806 Add information about dotnet_diagnostic.NUnit1032.additional_dispose_methods to the docs
  • #​795 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.11.1 to 17.12.0
  • #​793 chore: bump version

4.4.0

NUnit Analyzers 4.4 - November 13, 2024

This release of the NUnit Analyzers adds handling of Assert.IsAssignableFrom/Assert.IsNotAssignableFrom and
Assert.Positive/Assert.Negative. Also insertion of trivia for code fixes for NUnit2007 and NUnit2046
have been improved.

The release contains contributions from the following users (in alphabetical order):

  • @​manfred-brands
  • @​MCPtz
  • @​mikkelbu
  • @​verdie-g

Issues Resolved

Features and Enhancements

  • #​790 NUnit.Analyzers 4.3.0 missed an Assert.IsAssignableFrom that caused a build error after upgrading to latest NUnit 4.2.2
  • #​789 NUnit.Analyzers 4.3.0 missed an Assert.Positive that caused a build error after upgrading to latest NUnit 4.2.2

Bugs

  • #​784 Fix trivia for NUnit2046
  • #​783 NUnit2007 doesn't apply trivia correctly

Tooling, Process, and Documentation

  • #​788 chore: Bump NUnit to version 4.2.2
  • #​785 chore(deps): Bump NUnit3TestAdapter from 4.5.0 to 4.6.0
  • #​780 chore(deps): Bump CSharpIsNullAnalyzer from 0.1.495 to 0.1.593
  • #​778 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.10.0 to 17.11.1
  • #​776 chore: bump version
  • #​775 chore: Update release notes

4.3.0

NUnit Analyzers 4.3 - August 9, 2024

This release of the NUnit Analyzers contains some bug fixes to existing analyzers and code fixes - among other
improvements to trivia when using the code fix of NUnit2049.

For new features we now warn against using TestContext.Write as this will be obsolete in NUnit at some point;
NUnit1001 now recognises and check generic TestCase attributes; and we have added a new analyzer and code fix for
simplifying usages of ValuesAttribute.

The release contains contributions from the following users (in alphabetical order):

  • @​andrewimcclement
  • @​Bartleby2718
  • @​DrPepperBianco
  • @​KaiBNET
  • @​maettu-this
  • @​manfred-brands
  • @​mikkelbu
  • @​RenderMichael
  • @​SeanKilleen
  • @​trampster

Issues Resolved

Features and Enhancements

  • #​770 Add rule to detect calls to TestContext.Write methods and CodeFix to replace usages with Out.Write
  • #​767 Augment NUnit1001 to recognized and check generic TestCase attributes
  • #​755 New diagnostic: The Values attribute can be simplified.

Bugs

  • #​766 Error when TearDown method is defined in partial test classes - Syntax node is not within syntax tree
  • #​743 NUnit1032 (missing Dispose), if dispose is wrapped in "(… as IDisposable)?.Dispose()"
  • #​739 Null suppression does not work when Assert is fully qualified
  • #​713 Code fix for NUnit2049 places the comma at a wrong place and messes up indentation bug

Tooling, Process, and Documentation

  • #​764 Update the solution file
  • #​761 Update nunit.analyzers.nuspec to specify that NUnit.Analyzers v4 is intended to be used with NUnit 4.
  • #​756 error NUnit1032 is incorrect when InstancePerTestCase and constructor is used to initialize IDisposible
  • #​741 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.9.0 to 17.10.0 in /src
  • #​737 Update NUnit2013.md to fix code block
  • #​736 chore: bump version
  • #​734 Why dropping composite message formatting support also for Assert.Pass/Fail/... where there are no actual and constraint parameters?

4.2.0

NUnit Analyzers 4.2 - April 24, 2024

This release of the Analyzers extends NUnit2050 to also cover Assume and Nunit1032 to consider dispose of a type
having explicit interface implementation. Furthermore, named parameters are now handled correctly codefixes for
classical asserts, and NUnit2010 improves the logic for determining Equals methods.

The release contains contributions from the following users (in alphabetical order):

  • @​Bartleby2718
  • @​hazzik
  • @​maettu-this
  • @​manfred-brands
  • @​matode
  • @​mikkelbu

Issues Resolved

Features and Enhancements

  • #​731 Add test for wrapping conditional expression in parenthesis for NUnit2050
  • #​720 Replace UpdateStringFormatToFormattableString with String.Format
  • #​719 NUnit2050 should cover Assume
  • #​710 Nunit1032 - consider dispose of a type having explicit interface implementation

Bugs

  • #​728 NUnit2010 - do not consider Equals call if it doesn't override Object.Equals
  • #​712 [bug] Code fix for NUnit2005 does not correctly fix Assert.AreEqual if named parameters are used in unexpected order

Tooling, Process, and Documentation

  • #​733 Missing full stops added to NUnit2050
  • #​722 Use Markdown for CHANGES
  • #​708 chore: bump-version

4.1.0

NUnit Analyzers 4.1 - March 16, 2024

This release of the Analyzers extends the suppression of nullable warnings to also respect assumptions -
expressed via Assume.That. Also nullable warnings are suppressed even in the context of the
null-forgiving operator !, and NUnit2010 is extended to also cover is pattern expressions - e.g.
is null and more general integer patterns as is < 0 or >= 1.

The release contains contributions from the following users (in alphabetical order):

  • @​lahma
  • @​manfred-brands
  • @​mikkelbu
  • @​RenderMichael
  • @​TheBigNeo
  • @​verdie-g

Issues Resolved

Features and Enhancements

  • #​693 Possibly Null Reference Warning should be suppressed for Assume
  • #​691 Extent rule NUnit2010 to detect 'is null'
  • #​679 Null suppression doesn't work when the body has a null suppression

Bugs

  • #​700 CodeFix for Assert with null message causes ambiguous code.
  • #​689 Incorrect constraint model transformation for named parameters

Tooling, Process, and Documentation

  • #​697 chore: Bump NUnit to version 4.1.0
  • #​694 Switch to using license expression
  • #​690 chore(deps): Bump Microsoft.NET.Test.Sdk from 17.8.0 to 17.9.0
  • #​687 chore: Update release notes

4.0.1

NUnit Analyzers 4.0.1 - February 1, 2024

Small release that fixes a problem with the 4.0 release when combining TestCaseSource and CancelAfter.

The release contains contributions from the following users (in alphabetical order):

  • @​manfred-brands
  • @​mikkelbu
  • @​richardissimo

Issues Resolved

Bugs

  • #​685 error NUnit1029: The TestCaseSource provides '1' parameter(s), but the Test method expects '1' parameter(s)

Tooling, Process, and Documentation

  • #​684 chore: bump-version

4.0.0

NUnit Analyzers 4.0 - January 27, 2024

Version 4 of the NUnit analyzers drops the support for older releases of Visual Studio. I.e.
releases of Visual Studio that are older than Visual Studio 2019 16.3. In addition, this release
contains various bug fixes to existing analyzers, support of the CancelAfterAttribute
that was introduced in NUnit 4, and extends the codefix for NUnit2007 to also work when
.Within is used.

The release contains contributions from the following users (in alphabetical order):

  • @​Abrynos
  • @​gfoidl
  • @​Laniusexcubitor
  • @​MaceWindu
  • @​manfred-brands
  • @​mikkelbu
  • @​RenderMichael
  • @​SeanKilleen

Issues Resolved

Features and Enhancements

  • #​669 NUnit2007 does not provide codefix when .Within is used
  • #​609 Drop support for VS before 2019

Bugs

  • #​663 NUnit1027 fired when CancellationToken and [CancelAfter] is given
  • #​659 NUnit1032 throws an exception in a specific configuration
  • #​656 NUnit1028 warns about overridden methods
  • #​635 ArgumentException in DisposeFieldsAndPropertiesInTearDownAnalyzer

Tooling, Process, and Documentation

  • #​676 chore: markdownlint-cli2-config is removed use flag instead
  • #​668 chore(deps): Bump StyleCop.Analyzers.Unstable from 1.2.0.507 to 1.2.0.556
  • #​662 chore: Bump NUnit 4 to version 4.0.1
  • #​660 chore: Bump to NUnit 4
  • #​654 chore: Bump version
  • #​630 Update NUnit Analyzer docs to respect 120-character docs rule documentation
  • #​508 Restore "File version" and "Product version" in analyzer dlls

3.10.0

NUnit Analyzers 3.10 (and 2.10) - November 27, 2023

This release adds a couple of improvements to the analyzers:

  • Check that users don't accidentally specify CallerArgumentExpression parameters
  • Relax analyzers for added support for IAsyncEnumerable on *Source attributes

These improvements extend the functionality in the beta that added support for NUnit 4 and
for migrating to NUnit 4. Especially, the handling of the movement of classic asserts into a new namespace
NUnit.Framework.Legacy and of the improved assert result messages - for more information see
https://docs.nunit.org/articles/nunit/Towards-NUnit4.html. The analyzers can help updating the
classic assert and fix the assert messages.

The release contains contributions from the following users (in alphabetical order):

  • @​manfred-brands
  • @​mikkelbu
  • @​stevenaw

Issues Resolved

Features and Enhancements

  • #​639 Rule to check users don't accidentally specify CallerArgumentExpression parameters
  • #​634 Relax analyzers for added support for IAsyncEnumerable on *Source attributes

Tooling, Process, and Documentation

  • #​648 chore: Skip branch builds on PRs
  • #​644 chore: Update release notes for 3.10 beta
  • #​429 Drop the VSIX project

3.10.0-beta1

NUnit Analyzers 3.10-beta1 (and 2.9-beta1) - November 17, 2023

This beta adds support for the upcoming NUnit 4 - see pull request #​612 - which solves the following issues

  • #​620 Make Classic Conversion rule for CollectionAssert improvement
  • #​618 Make Classic Conversion rule for StringAssert
  • #​617 Update .Within makes no sense rule
  • #​610 Ensure Test Code works with NUnit4
  • #​606 Support for NUnit 4 legacy asserts
  • #​562 Warn use of params for assertion messages

The primary change is the handling of the movement of classic asserts into....

Description has been truncated

@dependabot
Bump coverlet.collector and 4 others
84f8f8e 
Bumps coverlet.collector from 6.0.0 to 6.0.4
Bumps Microsoft.NET.Test.Sdk from 17.6.0 to 17.14.1
Bumps NUnit from 3.13.3 to 4.3.2
Bumps NUnit.Analyzers from 3.6.1 to 4.9.2
Bumps NUnit3TestAdapter from 4.2.1 to 5.0.0

---
updated-dependencies:
- dependency-name: coverlet.collector
  dependency-version: 6.0.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 17.14.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: NUnit
  dependency-version: 4.3.2
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: NUnit.Analyzers
  dependency-version: 4.9.2
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: NUnit3TestAdapter
  dependency-version: 5.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Aug 3, 2025
@brych126 brych126 merged commit 9437214 into main Aug 3, 2025
1 check passed
@dependabot dependabot bot deleted the dependabot/nuget/DatabaseTests/DatabaseTestsAdoNet/multi-e190f49953 branch August 3, 2025 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@brych126