In Trino project we have a test using S3Mock.
It currently uses S3Mock version 3.0.1 but also works great with 3.12.0, the latest 3.x line available on Docker Hub.

When running With S3Mock 4.10.0 (latest 4.x currently available on Docker Hub) the test fails because a request to read tail 13 bytes from an empty object is rejected by S3Mock. FWIW such request is accepted by AWS S3.

This particular problem does not occur when running with S3Mock 3.0.1, 3.12.0, 4.5.0 or 4.8.0
and does occur when running with S3Mock 4.9.0 or 4.10.0.