Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Update testcontainers-go monorepo to v0.39.0 #71

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
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update testcontainers-go monorepo to v0.39.0 #71

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 12, 2025 •
edited
Loading

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Confidence
github.com/testcontainers/testcontainers-go v0.35.0 -> v0.39.0 age confidence
github.com/testcontainers/testcontainers-go/modules/localstack v0.35.0 -> v0.39.0 age confidence

Release Notes

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

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.

We fixed a typo in the exported field of the ContainerRequest struct, so users of the EnpointSettingsModifier type must update their code to use the EndpointSettingsModifier type instead.

🔒 Security
🚀 Features
🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
📦 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 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 Renovate
Copy link
Contributor Author

renovate bot commented May 12, 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):

  • 8 additional dependencies were updated

Details:

Package Change
dario.cat/mergo v1.0.1 -> v1.0.2
github.com/docker/docker v27.1.1+incompatible -> v28.3.3+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/opencontainers/image-spec v1.1.0 -> v1.1.1
golang.org/x/sys v0.32.0 -> v0.36.0

@renovate renovate bot requested review from a team as code owners May 12, 2025 20:35
@renovate renovate bot requested review from johncblandii and joe-niland May 12, 2025 20:35
@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented May 12, 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.

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in 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 from b35194c to 9cefcb0 Compare July 15, 2025 18:54
@renovate renovate bot changed the title Update testcontainers-go monorepo to v0.37.0 Update testcontainers-go monorepo to v0.38.0 Jul 15, 2025
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch from 9cefcb0 to a899a36 Compare September 19, 2025 11:12
@renovate renovate bot changed the title Update testcontainers-go monorepo to v0.38.0 Update testcontainers-go monorepo to v0.39.0 Sep 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@johncblandii johncblandii Awaiting requested review from johncblandii johncblandii is a code owner automatically assigned from cloudposse/contributors

@joe-niland joe-niland Awaiting requested review from joe-niland joe-niland is a code owner automatically assigned from cloudposse/contributors

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

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants