Bump org.assertj:assertj-core from 3.26.3 to 3.27.3

[dependabot]

Bumps org.assertj:assertj-core from 3.26.3 to 3.27.3.

Release notes

Sourced from org.assertj:assertj-core's releases.

v3.27.3

💥 Breaking Changes

Core

• Revert "Propagate common basetype for the extracting method" #3737

  The enhancement introduced with #3673 breaks existing code on Kotlin 1.9; therefore, it has been reverted.

  As Spring Boot 3.4 currently supports Kotlin 1.9, we want to keep the same compatibility on AssertJ 3.x, while AssertJ 4.x will require Kotlin 2.x.

  Existing code relying on the changes introduced with #3673 will no longer compile and should be refactored.

🐛 Bug Fixes

Core

• Fix StandardRepresentation regression for unquoted strings #3735

⚡ Improvements

Core

• Add Class info to class loading strategy failures #3746

❤️ Contributors

Thanks to all the contributors who worked on this release:

@​ccrvincent

v3.27.2

🐛 Bug Fixes

Core

• Restore support for null-valued maps when ignoring fields #3723

v3.27.1

🚫 Deprecated

Core

• Deprecate usingComparatorForFields and remove deprecated assertions from usingComparatorForType documentation #3711
• Deprecate hasCauseReference(Throwable) from Throwable assertions #3715

... (truncated)

Commits

• c928dd3 [maven-release-plugin] prepare release assertj-build-3.27.3
• f308d95 Fix StandardRepresentation regression for unquoted strings (#3735)
• e5959f4 Add Java and Kotlin release references
• 3eb809d Add Kotlin EAP reference
• b39a8cf Add Kotlin 2.1.10-RC
• e20e40d Add Class info to failure exception (#3746)
• 79b87f0 Revert "Propagate common basetype for the extracting method (#3673)" (#3737)
• bf439b3 chore(deps): bump com.diffplug.spotless:spotless-maven-plugin from 2.43.0 to ...
• 30936ca Restructure Kotlin tests, add DisplayNameGenerator
• b5b86cc Add Kotlin cross-version job (#3732)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[Bukama]

@dependabot rebase

[Bukama]

Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Command was /bin/sh -c cd '/Users/runner/work/maven-javadoc-plugin/maven-javadoc-plugin' && '/Users/runner/hostedtoolcache/Java_Adopt-OpenJ9_jdk/17.0.14-7/arm64/Contents/Home/bin/java' '-jar' '/Users/runner/work/maven-javadoc-plugin/maven-javadoc-plugin/target/surefire/surefirebooter-20250508094022503_3.jar' '/Users/runner/work/maven-javadoc-plugin/maven-javadoc-plugin/target/surefire' '2025-05-08T09-40-22_393-jvmRun1' 'surefire-20250508094022503_1tmp' 'surefire_0-20250508094022503_2tmp'
Error occurred in starting fork, check output in log
Process Exit Code: 255
Crashed tests:
org.apache.maven.plugins.javadoc.JavadocReportTest

[olamy]

segfault osx with openj9....

Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000018 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000002

does it really matter?

[olamy]

@dependabot rebase

[Bukama]

segfault osx with openj9....

Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000018 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000002

does it really matter?

For those who use it. But @bmarwell already got contact to IBM about this, right?

[bmarwell]

segfault osx with openj9....

Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000018 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000002

does it really matter?

For those who use it. But @bmarwell already got contact to IBM about this, right?

Yes, if that's the same as before: fixed in the next release.