chore(deps): update module github.com/testcontainers/testcontainers-go to v0.23.0 #437
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:
v0.19.0
->v0.23.0
Release Notes
testcontainers/testcontainers-go (github.com/testcontainers/testcontainers-go)
v0.23.0
Compare Source
What's Changed
🚀 Features
🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
📦 Dependency updates
v0.22.0
Compare Source
What's Changed
As a consequence of the bugs described in #1359, we had to bump the Docker version to a major version, which moved the
types.AuthConfig
type toregistry.AuthConfig
. We used that type as public API, therefore, our API has changed the signature of the method of an interface, which is used to build images from a Dockerfile. Please look at #1394 to understand the changes in theGetAuthConfigs
method.🚀 Features
📖 Documentation
🧹 Housekeeping
📦 Dependency updates
v0.21.0
Compare Source
What's Changed
🚀 Features
🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
📦 Dependency updates
v0.20.1
Compare Source
What's Changed
🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
v0.20.0
Compare Source
Maintainers' note
We want to inform you about an issue that occurred with the release,
v0.20.0
. Due to an unintended error, the git tags associated withv0.20.0
were created in an inconsistent state. As a result, the tags were removed and recreated to accurately reflect the intended release state. This situation could have affected users relying on the Go proxy cache during the short time window between the initial release and the tag correction.To address this issue, we have now created the patch release
v0.20.1
, which is based on the correct state of the project and provides a seamless transition fromv0.20.0
.To ensure that you have the latest updates, we recommend updating your dependencies to use
v0.20.1
instead ofv0.20.0
to ensure you have the correct and stable version.We apologise for any inconvenience this may have caused and appreciate your understanding. If you have any questions or encounter any issues, please don't hesitate to reach out to us.
Thank you for your continued support!
What's Changed
The signature of the
testcontainers.NewDockerClient
has changed in order to provide a simpler API for the future changes, and for that reason we were forced to break it and simplify its signature, returning the client and an error, instead of an instance of the Testcontainers properties and the host. At the same time, theTestContainersConfig
struct representing the configuration properties has been renamed toTestcontainersConfig
, which is brings consistency with the name of the project.🚀 Features
wait.HostPortStrategy
(#1039) @RiverPhillips🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
hashicorp/consul
in examples (#950) @eddumelendez📦 Dependency updates
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.