chore(deps): update dependency nunit.analyzers to v4 #27
Conversation
This file contains 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
force-pushed
the
renovate/nunit.analyzers-4.x
branch
from
54347d9 to
def9644
Compare
renovate
bot
force-pushed
the
renovate/nunit.analyzers-4.x
branch
from
def9644 to
3597351
Compare
renovate
bot
force-pushed
the
renovate/nunit.analyzers-4.x
branch
from
3597351 to
7e8ad10
Compare
renovate
bot
force-pushed
the
renovate/nunit.analyzers-4.x
branch
from
7e8ad10 to
8b28aa3
Compare
renovate
bot
force-pushed
the
renovate/nunit.analyzers-4.x
branch
2 times, most recently
from
3e6fdb6 to
b47c5d7
Compare
renovate
bot
force-pushed
the
renovate/nunit.analyzers-4.x
branch
from
b47c5d7 to
213d9ff
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:
3.9.0->4.3.0Release Notes
nunit/nunit.analyzers (NUnit.Analyzers)
v4.3.0: NUnit Analyzers 4.3 - August 9, 2024Compare Source
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.Writeas 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):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v4.2.0: NUnit Analyzers 4.2 - April 24, 2024Compare Source
NUnit Analyzers 4.2 - April 24, 2024
This release of the Analyzers extends NUnit2050 to also cover
Assumeand Nunit1032 to consider dispose of a typehaving explicit interface implementation. Furthermore, named parameters are now handled correctly codefixes for
classical asserts, and NUnit2010 improves the logic for determining
Equalsmethods.The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v4.1.0: NUnit Analyzers 4.1 - March 16, 2024Compare Source
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 thenull-forgiving operator
!, and NUnit2010 is extended to also coverispattern expressions - e.g.is nulland more general integer patterns asis < 0 or >= 1.The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v4.0.1: NUnit Analyzers 4.0.1 - February 1, 2024Compare Source
NUnit Analyzers 4.0.1 - February 1, 2024
Small release that fixes a problem with the 4.0 release when combining
TestCaseSourceandCancelAfter.The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Bugs
Tooling, Process, and Documentation
v4.0.0: NUnit Analyzers 4.0Compare Source
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
CancelAfterAttributethat was introduced in NUnit 4, and extends the codefix for NUnit2007 to also work when
.Withinis used.The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v3.10.0: NUnit Analyzers 3.10 (and 2.10)Compare Source
NUnit Analyzers 3.10 (and 2.10) - November 27, 2023
This release adds a couple of improvements to the analyzers:
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):
Issues Resolved
Features and Enhancements
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.