Update dependency NUnit.Analyzers to 4.9.2 #740
Conversation
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nunit.analyzers-4.x
branch
from
4ad0646 to
355908b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nunit.analyzers-4.x
branch
from
355908b to
5a4cba6
Compare
renovate
bot
force-pushed
the
renovate/nunit.analyzers-4.x
branch
from
5a4cba6 to
2edc211
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nunit.analyzers-4.x
branch
from
2edc211 to
28c9d54
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nunit.analyzers-4.x
branch
from
28c9d54 to
24612a1
Compare
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:
4.6.0->4.9.2Release Notes
nunit/nunit.analyzers (NUnit.Analyzers)
v4.9.2: NUnit Analyzers 4.9.2 - June 17, 2025Compare Source
NUnit Analyzers 4.9.2 - June 17, 2025
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.1: NUnit Analyzers 4.9.1 - June 12, 2025Compare Source
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.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
Bugs
Tooling, Process, and Documentation
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.