Skip to content

1.15.0-rc1

Pre-release
Pre-release
Compare
Choose a tag to compare
@github-actions github-actions released this 19 Jul 19:25
dd0d218

What's Changed

This is a release candidate build for version 1.15.0, including a large number of small but noticeable changes.

At least one further release candidate build is expected before 1.15.0 final, and some API changes may still be made. We would encourage users to upgrade to this release candidate version if possible, and to give us feedback on any issues that are encountered.

Notable changes

  • Add a rootless Docker strategy (#2985) @bsideup. This allows Testcontainers to be used with Docker's rootless mode. All Testcontainers' features and modules are compatible with Docker rootless mode, but we would appreciate feedback on unidentified edge cases.

  • Deprecate ambiguous constructors (#2839) @rnorth. This change affects the majority of constructors for container classes. This is intended to encourage users to specify an exact docker image and tag for dependencies, rather than relying on a (potentially outdated) default image chosen by Testcontainers.

    • new XyzContainer()-style and new XyzContainer(String)-style constructors are deprecated throughout, in favour of a strongly typed new XyzContainer(DockerImageName)-style constructor.
    • Users should identify an appropriate Docker image for their test dependencies, and use as follows: new XyzContainer( DockerImageName.parse( "the/image:tag" ) ).
    • We expect to make some further improvements in this area before the final 1.15.0 release.
  • Un-shade docker-java-api (#2882) @bsideup. This change follows some significant refactoring of the docker-java library, and should resolve various issues associated with shading of dependencies.

  • New optional transport based on Apache HttpClient5. This is a very promising transport that most probably will become the default in future versions of Testcontainers. You can give it a try by putting transport.type = httpclient5 to $HOME/.testcontainers.properties.

⚠️ Breaking API changes

While we expect that the vast majority of users will notice no difference, these changes can be considered breaking, so warrant special mention:

☠️ Deprecations

🚀 Features & Enhancements

🐛 Bug Fixes

📖 Documentation

🧹 Housekeeping

📦 Dependency updates

Click to expand...