Skip to content

chore(deps): update module github.com/testcontainers/testcontainers-go to v0.40.0#251

Merged
raffis merged 1 commit intomasterfrom
renovate/testcontainers-go-monorepo
Nov 18, 2025
Merged

chore(deps): update module github.com/testcontainers/testcontainers-go to v0.40.0#251
raffis merged 1 commit intomasterfrom
renovate/testcontainers-go-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 30, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/testcontainers/testcontainers-go v0.35.0 -> v0.40.0 age adoption passing confidence

Release Notes

testcontainers/testcontainers-go (github.com/testcontainers/testcontainers-go)

v0.40.0

Compare Source

What's Changed
⚠️ Breaking Changes

The below modules receive a breaking change in the signature of their functional options, as now all of them return an error when needed (returning nil for success). Therefore, you're only affected when assigning the options to variables.

  • Old: type Option func(*options)
  • New: type Option func(*options) error
🚀 Features
🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
📦 Dependency updates

v0.39.0

Compare Source

What's Changed

🚀 Features

🐛 Bug Fixes

📖 Documentation

  • docs: clarify no client SDKs in production modules/images, in contributing.md (#​3279) @​nimdrak

🧹 Housekeeping

📦 Dependency updates

v0.38.0

Compare Source

What's Changed

⚠️ Breaking Changes

The breaking change comes as a behaviour that has been removed: the readiness check for the exposed ports. It led to flakiness and for that reason we removed it.

Only for users of the testcontainers.NewRawCommand function to create executables in containers, that are assigning the function to a variable. We added a variadic argument to the signature, so the rest of the users won't be affected by this breaking change.

  • chore(deps)!: bump github.com/docker/docker from 28.1.1+incompatible to 28.2.2+incompatible (#​3194) @​mdelapenya

Implementers of the testcontainers.ImageBuildInfo interface, would see that testcontainers.BuildOptions has changed its signature to use non-deprecated types from docker/docker:

type ImageBuildInfo interface {
- 	 BuildOptions() (types.ImageBuildOptions, error) // converts the ImageBuildInfo to a types.ImageBuildOptions
+        BuildOptions() (build.ImageBuildOptions, error) // converts the ImageBuildInfo to a build.ImageBuildOptions

Also users of the testcontainers.FromDockerfile struct will receive this breaking change, as the BuildOptionsModifier fields has changed:

- BuildOptionsModifier func(*types.ImageBuildOptions)
+ BuildOptionsModifier func(*build.ImageBuildOptions)

🔒 Security

🚀 Features

🐛 Bug Fixes

📖 Documentation

🧹 Housekeeping

📦 Dependency updates

v0.37.0

Compare Source

What's Changed

🔒 Security

  • chore(deps): bump golang.org/x/crypto from 0.31.0 to 0.35.0 in /modules/aerospike (#​3105) @​dependabot[bot]
  • chore(pulsar): bump github.com/apache/pulsar-client-go from 0.10.0 to 0.14.0 in /modules/pulsar (#​3100) @​mdelapenya
  • chore(clickhouse): bump github.com/ClickHouse/clickhouse-go/v2 from 2.20.0 to 2.34.0 in /modules/clickhouse (#​3099) @​dependabot[bot]
  • security(compose): upgrade github.com/docker/compose/v2 to fix security vulnerability (#​3095) @​sigi-glovebox

🚀 Features

🐛 Bug Fixes

📖 Documentation

🧹 Housekeeping

📦 Dependency updates

v0.36.0

Compare Source

What's Changed

⚠️ Breaking Changes

  • feat(azure)!: add Azurite, EventHubs and ServiceBus in the new Azure module, deprecating the old Azurite module (#​3008) @​mdelapenya

Users of the old Azurite module must update their code to use the new Azure module instead, which contains the same functionality under the azurite sub-package.
We took this opportunity to remove the unnecessarily exported Settings field from the Azurite container type,
so users of the Azurite container type must update their code to simply do not use that field.

  • chore(deps)!: bump github.com/docker/docker from 27.1.1+incompatible to 28.0.1+incompatible (#​3017) @​dependabot[bot]

Bumping the Docker package to a newer major version came with lots of benefits, but also some breaking changes. For that reason, users of the following
container methods and types must update their code to use the new types and methods instead:

  • Container.Inspect: the return type has been changed from types.ContainerJSON to container.InspectResponse.
  • Container.State: the return type has been changed from types.ContainerState to container.State.
  • DockerProvider.ContainerFromType: the method signature has been changed to accept a container.Summary instead of a types.Container.
    At the same time, if consuming Docker types or methods, users must update their code to use the new types and methods instead.
    As a good rule of thumb, users of the "github.com/docker/docker/api/types" package must update their code to use "github.com/docker/docker/api/types/container" instead.

Users of the deprecated DockerCompose type from the compose module must update their code to use DockerComposer instead.
The former unexported dockerCompose type has been renamed to DockerCompose. This breaking change was done because returning
an un-exported type from a constructor function limits the flexibility and usability of the returned instance. Callers could use
the exported methods, but could not declare variables of that type, pass instances to other functions, or embed them in structs
without exposing the constructor itself. This breaking change was needed to improve the usability of the compose module.

Users of the testcontainers.Logging variable and the testcontainers.TestLogger function must update their code to use the new log.Default() logger instance and the log.TestLogger() function instead, and
users of the testcontainers.Logger interface must update their code to use the new log.Logger interface instead.
The new log package allows users to set a custom logger instance calling the log.SetDefault(l log.Logger) function.
This breaking change was needed to improve the usability of the logging functionality when using the testcontainers package.

Users of the NATS module and the ConnectionString type must remove the variadic arguments from the ConnectionString method. This breaking change was needed because those arguments weren't in use.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner March 30, 2025 13:28
@renovate
Copy link
Contributor Author

renovate bot commented Mar 30, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: go get -t ./...
go: module github.com/testcontainers/testcontainers-go@v0.40.0 requires go >= 1.24.0; switching to go1.24.10
go: downloading go1.24.10 (linux/amd64)
go: download go1.24.10: golang.org/toolchain@v0.0.1-go1.24.10.linux-amd64: verifying module: checksum database disabled by GOSUMDB=off

@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 3 times, most recently from 4768d92 to 663d275 Compare April 5, 2025 01:53
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 2 times, most recently from 508110b to ceac4d7 Compare April 14, 2025 12:05
@coderabbitai
Copy link

coderabbitai bot commented Apr 14, 2025 •
edited
Loading

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 2 times, most recently from d10d915 to 481eb42 Compare April 16, 2025 07:43
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 8 times, most recently from 62cd67f to f732f4f Compare April 28, 2025 13:44
@renovate renovate bot changed the title chore(deps): update module github.com/testcontainers/testcontainers-go to v0.36.0 chore(deps): update module github.com/testcontainers/testcontainers-go to v0.37.0 Apr 28, 2025
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 5 times, most recently from 79bf227 to 51678d1 Compare May 10, 2025 22:23
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 3 times, most recently from 0a460bd to edd682f Compare May 17, 2025 21:44
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 5 times, most recently from 0612e66 to b4d95b6 Compare July 7, 2025 10:13
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch from b4d95b6 to 656891e Compare July 18, 2025 13:36
@renovate renovate bot changed the title chore(deps): update module github.com/testcontainers/testcontainers-go to v0.37.0 chore(deps): update module github.com/testcontainers/testcontainers-go to v0.38.0 Jul 18, 2025
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 6 times, most recently from 5e7fa93 to 2134afe Compare July 25, 2025 05:15
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 2 times, most recently from cb07cc6 to 0b5c2eb Compare August 2, 2025 07:28
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 2 times, most recently from 465f60b to 8ad20fc Compare August 8, 2025 00:37
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch from 8ad20fc to d0791ae Compare September 22, 2025 09:35
@renovate renovate bot changed the title chore(deps): update module github.com/testcontainers/testcontainers-go to v0.38.0 chore(deps): update module github.com/testcontainers/testcontainers-go to v0.39.0 Sep 22, 2025
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch 6 times, most recently from 0d4f63f to 5f3bb80 Compare October 23, 2025 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@raffis raffis raffis approved these changes

Assignees

No one assigned

Labels

dependencies gomod size/XS

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@raffis