Ruby 3.3+ emits a warning from the minitest version we were running because it was using mutex_m from the stdlib without declaring it as a dependency. That library is moving out to a bundled gem, so needs to be depended on to make it available in Ruby 3.4+. Update minitest to squash the warning (they removed the usage of mutex_m entirely it seems.)
Whilst we're in here, update all the gemfiles to the latest bundler.
If you get failing tests locally with bundle exec rake test:all, ensure the images have been rebuilt with bundle exec rake build:all first. For some reason updating the Gemfile isn't triggering a rebuild before we run the tests in the container from the image. (Which is what leads to the test failure - bundler is whinging the lockfile isn't updated compared to what's installed in the image.)
What?
Why?
Ruby 3.3+ emits a warning from the minitest version we were running because it was using
mutex_mfrom the stdlib without declaring it as a dependency. That library is moving out to a bundled gem, so needs to be depended on to make it available in Ruby 3.4+. Update minitest to squash the warning (they removed the usage of mutex_m entirely it seems.)Whilst we're in here, update all the gemfiles to the latest bundler.
If you get failing tests locally with
bundle exec rake test:all, ensure the images have been rebuilt withbundle exec rake build:allfirst. For some reason updating the Gemfile isn't triggering a rebuild before we run the tests in the container from the image. (Which is what leads to the test failure - bundler is whinging the lockfile isn't updated compared to what's installed in the image.)