Update testcontainersVersion to v1.17.1 (minor) #1955
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.16.3
->1.17.1
1.16.3
->1.17.1
Release Notes
testcontainers/testcontainers-java
v1.17.1
Compare Source
What's Changed
🐛 Bug Fixes
StackOverflowError
inDockerClientFactory#client
(#5262) @bsideup📖 Documentation
v1.17.0
Compare Source
What's Changed
Highlights
This new version of Testcontainers comes packed with many new features and quality-of-life improvements, so we appropriately bumped the version to
1.17.0
.🐝 New Module: HiveMQ (#4797) @YannickWeber
Having started its Open Source life as its own 3rd-party Testcontainers library, we are very happy to welcome HiveMQ into the main repository.
Now, using HiveMQ as part of your integration tests is as simple as a couple of lines of Java code:
Check out the docs to learn more about its many features!
💀 Ryuk JVM mode (#4959) (#4960) @bsideup
Many Testcontainers user love the convenience Ryuk brings to Testcontainers: No matter what you do in your integration tests, Ryuk has got you covered and will cleanup all Docker resources created by Testcontainers after your test run is finished.
But some users operate Testcontainers in environments which do not support our container-based Ryuk implementation. So far their only option was to disable Ryuk alltogether.
Coming with this release, Testcontainers will now fallback to a JVM based resource-cleanup implementation in case of Ryuk being disabled.
While this won't be as robust as the Ryuk container based implementation in all circumstances, it is nevertheless a great addition and acts as a useful compromise.
🚀 Features & Enhancements
getContainerIpAddress
(#5247) @kiviewcheckAndPullImage
withRemoteDockerImage
(#5148) @bsideupgetTestHostIpAddress
andgetContainerIpAddress
(#5149) @bsideup🐛 Bug Fixes
📖 Documentation
Byzer
. (#5125) @hellozeppINCUBATING
note from CockroachDB module docs (#4963) @kiview🧹 Housekeeping
📦 Dependency updates
Click to expand...
docker-java
3.2.13 (#5045) @bsideupConfiguration
📅 Schedule: "every weekend" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by WhiteSource Renovate. View repository job log here.