Skip to content

Commit

Permalink
Merge pull request #682 from nunit/release4.0
Browse files Browse the repository at this point in the history
chore: Update release notes
  • Loading branch information
mikkelbu authored Jan 27, 2024
2 parents 87e452f + 7056b7f commit bb132f0
Showing 1 changed file with 41 additions and 1 deletion.
42 changes: 41 additions & 1 deletion CHANGES.txt
Original file line number Diff line number Diff line change
@@ -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
Expand Down

0 comments on commit bb132f0

Please sign in to comment.