> I think this regressed. While it seems the behavior was fixed in 3.23.1 (https://github.com/assertj/assertj/commit/c487af4cdb37b01103e4ec0f9971c9a53c766db5), I can reproduce the original issue in 3.27.6. _Originally posted by @sherfert in [#864](https://github.com/assertj/assertj/issues/864#issuecomment-3804628164)_