build(deps-dev): bump nl.jqno.equalsverifier:equalsverifier from 4.2.5 to 4.4

[dependabot]

Bumps nl.jqno.equalsverifier:equalsverifier from 4.2.5 to 4.4.

Release notes

Sourced from nl.jqno.equalsverifier:equalsverifier's releases.

Release equalsverifier-4.4

For a list of changes in this version, see CHANGELOG.md.

Release equalsverifier-4.3.1

For a list of changes in this version, see CHANGELOG.md.

Release equalsverifier-4.3

For a list of changes in this version, see CHANGELOG.md.

Release equalsverifier-4.2.6

For a list of changes in this version, see CHANGELOG.md.

Changelog

Sourced from nl.jqno.equalsverifier:equalsverifier's changelog.

[4.4] - 2026-02-21

Added

• Proper support for JEP 500: "Prepare to Make Final Mean Final", where the JDK emits a warning (or, if so configured, throws an exception) when final fields are mutated.
  • #withFactory() method to provide instances to EqualsVerifier so it doesn't have to mutate final fields;
  • Overloads for #withRedefinedSuperclass() and #withRedefinedSubclass() to do the same;
  • Overloads for #withPrefabValues() and #withPrefabValuesForField() where you explicitly provide a copy of the "red" value, because EqualsVerifier will not be able to make a copy of that value without using final field mutation.
  • .set(Mode.finalMeansFinal() so EqualsVerifier refuses to mutate final fields even when still possible: this is useful when migrating to a newer JDK where this is an issue.
  • Documentation: see the chapter on this subject in the manual.
• Prefab values for java.lang.Number.

Changed

• For doubles and floats, EqualsVerifier now uses 0.0 and -0.0 instead of NaN to test edge case handling without triggering precondition exceptions. For boxed Double/Float, it now suggests equals() over Double.compare()/Float.compare() (they behave identically).

[4.3.1] - 2026-01-24

Changed

• EqualsVerifier now respects Kotlin's data class contract: properties declared in the class body are assumed not to take part in equals() and hashCode(). (Issue 1159; thanks Sogilis Team!)

[4.3] - 2026-01-01

Changed

• Restored original behaviour for multiple predicate-based ScanOption exceptions. (Issue 1167; thanks Mark!)

[4.2.6] - 2025-12-30

Fixed

• If first permitted and non-abstract subclass of a sealed type has a recursion, EqualsVerifier throws RecursionException instead of trying the second permitted non-abstract subclass. (Issue 1081)

Changed

• Avoids potential parameter order bug when instantiating records. (Issue 1160; thanks lycoris106!)
• More performance improvements.

Commits

• a6d4e87 Bumps version to 4.4
• 17a917a Updates CHANGELOG for release
• 0df7252 Updates CHANGELOG
• 2842295 Merge pull request #1181 from jqno/final-means-final
• 23a370f Makes FieldMutator exception more explicit
• fea304d Fixes several mutation tests
• 37e7800 Fixes several mutation tests
• 676c009 Fixes several mutation tests
• c9005a4 Runs PITest with Java 26
• 099aff9 Merge pull request #1182 from jqno/dependabot/bundler/docs/nokogiri-1.19.1
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codacy-production]

Codacy's Analysis Summary

0 new issue (≤ 0 minor issue)
0 new security issue
0 complexity
0 duplications

Review Pull Request in Codacy →

✨ AI Reviewer available: add the codacy-review label to get contextual insights without leaving GitHub.