chore: update dependency nunit.analyzers to 4.11.2#656
chore: update dependency nunit.analyzers to 4.11.2#656olavloite merged 1 commit intogoogleapis:mainfrom
Conversation
Summary of ChangesHello @renovate-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates the NUnit.Analyzers package to version 4.11.2. While keeping dependencies up-to-date is good practice, this major version upgrade introduces a compatibility issue. NUnit.Analyzers v4.x requires NUnit v4.x, but the projects are still using NUnit v3.14.0. This mismatch can lead to incorrect behavior from the analyzers. I've left comments in the project files recommending that the NUnit package also be upgraded to a compatible version to resolve this.
spanner-ado-net/spanner-ado-net-samples-tests/spanner-ado-net-samples-tests.csproj
Outdated
Show resolved
Hide resolved
spanner-ado-net/spanner-ado-net-tests/spanner-ado-net-tests.csproj
Outdated
Show resolved
Hide resolved
10e7a05 to
eef0817
Compare
eef0817 to
cc45129
Compare
This PR contains the following updates:
4.2.0→4.11.2Release Notes
nunit/nunit.analyzers (NUnit.Analyzers)
v4.11.2: NUnit Analyzers 4.11.2 - November 2, 2025Compare Source
NUnit Analyzers 4.11.2 - November 2, 2025
This release of the NUnit Analyzers fixes a problem in the
NUnit2057analyzer for unnecessary use of lambdaexpressions. The release also extends
NUnit2021so that it can determining ifIs.NaNorIs.Not.NaNconstraintsare used on incompatible types.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
v4.11.1Compare Source
This release of the NUnit Analyzers fixes a regression related to the analysis of nullable enum parameters in
NUnit1001andNUnit1031. The release also contains a new analyzer and codefix for unnecessary usage of lambdaexpressions in asserts.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
v4.11.0: NUnit Analyzers 4.11 - October 28, 2025Compare Source
NUnit Analyzers 4.11 - October 28, 2025
This release of the NUnit Analyzers includes improvements and fixes related to
IDisposablehandling and initializationin
SetUpandOneTimeSetUpmethods. It also introduces the ability to configure additional methods that should betreated as
SetUpandTearDownmethods by the analyzers. This can be done in the.editorconfig, and there are fourconfigurations for this:
dotnet_diagnostic.NUnit.additional_setup_methodsdotnet_diagnostic.NUnit.additional_teardown_methodsdotnet_diagnostic.NUnit.additional_one_time_setup_methodsdotnet_diagnostic.NUnit.additional_one_time_teardown_methodsEach configuration accepts a list of method names, separated by commas, semicolons, or spaces. For example:
dotnet_diagnostic.NUnit.additional_setup_methods = CustomSetup, MyInitAs in recent releases, a major part of this work was contributed by @manfred-brands.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v4.10.0: NUnit Analyzers 4.10 - August 9, 2025Compare Source
NUnit Analyzers 4.10 - August 9, 2025
This release of the NUnit Analyzers contains some minor improvements to NUnit2050, NUnit2056, and NUnit2007 as well
as some improvements to existing tests. Once again, @manfred-brands was responsible for the majority of the work.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Bugs
Tooling, Process, and Documentation
v4.9.2Compare Source
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.1Compare Source
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
v4.6.0: NUnit Analyzers 4.6 - January 9, 2025Compare Source
NUnit Analyzers 4.6 - January 9, 2025
This release contains two improvements: Allowing
NUnit1001to understandDateOnlyandTimeOnlyparameters inTestCaseUsageand makingNUnit2045supportAssert.EnterMultipleScope(introduced in NUnit version 4.2).The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Tooling, Process, and Documentation
v4.5.0: NUnit Analyzers 4.5 - December 22, 2024Compare Source
NUnit Analyzers 4.5 - December 22, 2024
The release primarily fixes a problem with the NUnit Analyzers when used with NUnit 4.3.1 - see #811 for more
information. In additional, we have also added some smaller improvements and bug fixes.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
v4.4.0: NUnit Analyzers 4.4 - November 13, 2024Compare Source
NUnit Analyzers 4.4 - November 13, 2024
This release of the NUnit Analyzers adds handling of
Assert.IsAssignableFrom/Assert.IsNotAssignableFromandAssert.Positive/Assert.Negative. Also insertion of trivia for code fixes forNUnit2007andNUnit2046have been improved.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
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
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.