Skip to content

fix(deps): update testcontainers-go monorepo to v0.40.0 #256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update testcontainers-go monorepo to v0.40.0 #256

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link

@renovate renovate bot commented Oct 27, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
github.com/testcontainers/testcontainers-go v0.35.0 -> v0.40.0 age confidence
github.com/testcontainers/testcontainers-go/modules/postgres v0.35.0 -> v0.40.0 age 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 o

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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
Copy link
Author

renovate bot commented Oct 27, 2025 •
edited
Loading

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 6 additional dependencies were updated

Details:

Package Change
github.com/docker/docker v27.1.1+incompatible -> v28.5.1+incompatible
github.com/docker/go-connections v0.5.0 -> v0.6.0
github.com/magiconair/properties v1.8.7 -> v1.8.10
github.com/moby/sys/sequential v0.5.0 -> v0.6.0
github.com/moby/sys/user v0.1.0 -> v0.4.0
github.com/yusufpapurcu/wmi v1.2.3 -> v1.2.4

external-secrets-bot[bot]
external-secrets-bot bot approved these changes Oct 27, 2025
View reviewed changes
Copy link

@external-secrets-bot external-secrets-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because this is so small 🙈

@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch from 3baa9e7 to 458c46c Compare October 27, 2025 17:29
external-secrets-bot[bot]
external-secrets-bot bot approved these changes Oct 27, 2025
View reviewed changes
Copy link

@external-secrets-bot external-secrets-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because this is so small 🙈

@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch from 458c46c to 411e065 Compare October 27, 2025 17:31
external-secrets-bot[bot]
external-secrets-bot bot approved these changes Oct 27, 2025
View reviewed changes
Copy link

@external-secrets-bot external-secrets-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because this is so small 🙈

@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch from 411e065 to 8f38506 Compare November 6, 2025 12:10
@renovate renovate bot changed the title fix(deps): update testcontainers-go monorepo to v0.39.0 fix(deps): update testcontainers-go monorepo to v0.40.0 Nov 6, 2025
@github-actions github-actions bot added size/XXS and removed size/XXS labels Nov 6, 2025
external-secrets-bot[bot]
external-secrets-bot bot approved these changes Nov 6, 2025
View reviewed changes
Copy link

@external-secrets-bot external-secrets-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because this is so small 🙈

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@external-secrets-bot external-secrets-bot[bot] external-secrets-bot[bot] approved these changes

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

size/XXS

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants