From 7056b7fcda0937ee46a14d3c307e6863cae1a23e Mon Sep 17 00:00:00 2001 From: Mikkel Nylander Bundgaard Date: Sat, 27 Jan 2024 22:10:48 +0100 Subject: [PATCH] chore: Update release notes --- CHANGES.txt | 42 +++++++++++++++++++++++++++++++++++++++++- 1 file changed, 41 insertions(+), 1 deletion(-) diff --git a/CHANGES.txt b/CHANGES.txt index ed1b1e56..cebaa261 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,44 @@ -NUnit Analyzers 3.10 (and 2.10) - November 27, 2023 +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 + + +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