Update dependency NUnit.Analyzers to 3.10.0 #2969
Open
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
changed the title
renovate
bot
force-pushed
the
renovate/nunit.analyzers-3.x
branch
from
a51af55 to
c71fe3d
Compare
renovate
bot
force-pushed
the
renovate/nunit.analyzers-3.x
branch
from
c71fe3d to
ade3a3f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nunit.analyzers-3.x
branch
from
ade3a3f to
58de5c0
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nunit.analyzers-3.x
branch
from
58de5c0 to
60efeaf
Compare
renovate
bot
force-pushed
the
renovate/nunit.analyzers-3.x
branch
2 times, most recently
from
09a842d to
4b4ee6a
Compare
renovate
bot
force-pushed
the
renovate/nunit.analyzers-3.x
branch
from
4b4ee6a to
175a99d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/nunit.analyzers-3.x
branch
from
175a99d to
9ea3960
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.5.0->3.10.0Release Notes
nunit/nunit.analyzers (NUnit.Analyzers)
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
v3.9.0: NUnit Analyzers 3.9 (and 2.9)Compare Source
NUnit Analyzers 3.9 (and 2.9) - October 27, 2023
This release contains bugfixes to NUnit2045 - Use Assert.Multiple - and NUnit1032 -
An IDisposable field/property should be Disposed in a TearDown method - and corrects
a StackOverflowException when tests calls methods recursively.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Bugs
v3.8.0: NUnit Analyzers 3.8 (and 2.8)Compare Source
NUnit Analyzers 3.8 (and 2.8) - September 25, 2023
This release contains a fix to the WithinUsageAnalyzer and handling of false duplicates when
combining NUnit1032 - An IDisposable field/property should be Disposed in a TearDown method -
with LifeCycle.InstancePerTestCase.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v3.7.0: NUnit Analyzers 3.7 (and 2.7)Compare Source
NUnit Analyzers 3.7 (and 2.7) - September 16, 2023
This release contains a lot of improvements and corrections to the supression of non-nullable fields and properties
that are assigned in setup methods (and not in constructors). We have also added suppression of:
The release also contain some improvements to the performance of the analyzers by avoid repeated calls to
GetTypeByMetadataName. Also ValuesAttribute is now also handled by the analyzer in a similar manner as TestCaseAttribute.
Most of the work done in this release have either been driven by or made by @manfred-brands.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v3.6.1: NUnit Analyzers 3.6.1 (and 2.6.1) - March 10, 2023Compare Source
NUnit Analyzers 3.6.1 (and 2.6.1) - March 10, 2023
This release of the NUnit Analyzers contain a single bug fix and some updates of dependencies.
The bug fix removes a false from NUnit1030 - "The type of parameter provided by the TestCaseSource
does not match the type of the parameter in the Test method" - when using TestCaseParameters.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Bugs
Tooling, Process, and Documentation
v3.6.0: NUnit Analyzers 3.6 (and 2.6)Compare Source
NUnit Analyzers 3.6 (and 2.6) - February 21, 2023
This release of the NUnit Analyzers improves on the analysis of nullable reference types - in particular
in case of null coalescing operator and tuple deconstruction assignments.
The release also adds two new diagnostics for the TestCaseSource attribute. The diagnostics examines the test data returned
from the TestCaseSource:
In addition, the release also contains some bug fixes to existing analyzers, and we have added a GitHub Actions workflow
and status badge.
The release contains contributions from the following users (in alphabetical order):
The majority of the code contributions were provided by @manfred-brands.
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 is behind base branch, 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.