Bump NUnit.Analyzers from 4.1.0 to 4.2.0 in the nuget-dependencies group

[dependabot]

Bumps the nuget-dependencies group with 1 update: NUnit.Analyzers.

Updates NUnit.Analyzers from 4.1.0 to 4.2.0

Release notes

Sourced from NUnit.Analyzers's releases.

NUnit Analyzers 4.2 - April 24, 2024

This release of the Analyzers extends NUnit2050 to also cover Assume and Nunit1032 to consider dispose of a type having explicit interface implementation. Furthermore, named parameters are now handled correctly codefixes for classical asserts, and NUnit2010 improves the logic for determining Equals methods.

The release contains contributions from the following users (in alphabetical order):

• @​Bartleby2718
• @​hazzik
• @​maettu-this
• @​manfred-brands
• @​matode
• @​mikkelbu

Issues Resolved

Features and Enhancements

• #731 Add test for wrapping conditional expression in parenthesis for NUnit2050
• #720 Replace UpdateStringFormatToFormattableString with String.Format
• #719 NUnit2050 should cover Assume
• #710 Nunit1032 - consider dispose of a type having explicit interface implementation

Bugs

• #728 NUnit2010 - do not consider Equals call if it doesn't override Object.Equals
• #712 [bug] Code fix for NUnit2005 does not correctly fix Assert.AreEqual if named parameters are used in unexpected order

Tooling, Process, and Documentation

• #733 Missing full stops added to NUnit2050
• #722 Use Markdown for CHANGES
• #708 chore: bump-version

Changelog

Sourced from NUnit.Analyzers's changelog.

# NUnit Analyzers 4.2 - April 24, 2024

This release of the Analyzers extends NUnit2050 to also cover Assume and Nunit1032 to consider dispose of a type having explicit interface implementation. Furthermore, named parameters are now handled correctly codefixes for classical asserts, and NUnit2010 improves the logic for determining Equals methods.

The release contains contributions from the following users (in alphabetical order):

• @​Bartleby2718
• @​hazzik
• @​maettu-this
• @​manfred-brands
• @​matode
• @​mikkelbu

Issues Resolved

Features and Enhancements

• #731 Add test for wrapping conditional expression in parenthesis for NUnit2050
• #720 Replace UpdateStringFormatToFormattableString with String.Format
• #719 NUnit2050 should cover Assume
• #710 Nunit1032 - consider dispose of a type having explicit interface implementation

Bugs

• #728 NUnit2010 - do not consider Equals call if it doesn't override Object.Equals
• #712 [bug] Code fix for NUnit2005 does not correctly fix Assert.AreEqual if named parameters are used in unexpected order

Tooling, Process, and Documentation

• #733 Missing full stops added to NUnit2050
• #722 Use Markdown for CHANGES
• #708 chore: bump-version

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 the null-forgiving operator !, and NUnit2010 is extended to also cover is pattern expressions - e.g. is null and more general integer patterns as is < 0 or >= 1.

The release contains contributions from the following users (in alphabetical order):

• @​lahma
• @​manfred-brands
• @​mikkelbu
• @​RenderMichael
• @​TheBigNeo
• @​verdie-g

Issues Resolved

Features and Enhancements

... (truncated)

Commits

• 2c5a93e Merge pull request #735 from nunit/release4.2
• 5fe049b chore: Update release notes
• 37ee849 Merge pull request #733 from maettu-this/maettu-this_missing-full-stops-added
• dfe15f5 Missing full stops added to NUnit2050
• 07d8594 Sometimes we cannot convert message+args into a formattable string. (#725)
• d551aac Merge pull request #730 from manfred-brands/Issue728
• f9cac1d Merge pull request #731 from manfred-brands/Issue729
• acb700b Add test for wrapping conditional expression in parenthesis for NUnit2050
• 52bb832 NUnit2010: Exclusions
• d14cc57 Fix logic around out-of-order arguments for classic assertions (#712) (#716)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions