Skip to content
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.

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

fix(deps): update module github.com/testcontainers/testcontainers-go to v0.35.0 #18

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 10, 2025

This PR contains the following updates:

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

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v0.35.0

Compare Source

What's Changed

⚠️ Breaking Changes

The container.Terminate(ctx) method now accepts an extra variadic argument with termination options. The breaking change only affects users assigning this method to a variable, receiving a compile-time error. The rest of the users will simply satisfy the new signature with an empty slice of termination options.

The ShouldPrintBuildLog function of the ContainerRequest has been removed. Instead, a BuildLogWriter function appears, that returns the user-defined io.Writer for writing the image-build logs. In case there is no writer, and the FromDockerfile.PrintBuildLog is set to true, os.Stderr would be used.

Users of the GCloud module and the WithProjectID option must handle the error that this option now returns. This can be get at compile time, as all the functional options for container customisers must return an error.

The types and functions of the PortForwarder type are now private, as they are implementation details of the library, so there is no need for them to be exposed.

Usages of the GenericProviderOptions.DefaultNetwork field must be removed, as this field is now private. The container runtime should provide the default network under the hood.

🔒 Security

🚀 Features

🐛 Bug Fixes

📖 Documentation

🧹 Housekeeping

📦 Dependency updates

v0.34.1

Compare Source


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.


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

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

Copy link
Contributor Author

renovate bot commented Jan 10, 2025

ℹ 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):

  • 2 additional dependencies were updated

Details:

Package Change
golang.org/x/crypto v0.22.0 -> v0.31.0
golang.org/x/sys v0.21.0 -> v0.28.0

@renovate renovate bot changed the title fix(deps): update module github.com/testcontainers/testcontainers-go to v0.35.0 fix(deps): update module github.com/testcontainers/testcontainers-go to v0.35.0 - autoclosed Feb 7, 2025
@renovate renovate bot closed this Feb 7, 2025
@renovate renovate bot deleted the renovate/testcontainers-go-monorepo branch February 7, 2025 02:15
@renovate renovate bot changed the title fix(deps): update module github.com/testcontainers/testcontainers-go to v0.35.0 - autoclosed fix(deps): update module github.com/testcontainers/testcontainers-go to v0.35.0 Feb 7, 2025
@renovate renovate bot reopened this Feb 7, 2025
@renovate renovate bot force-pushed the renovate/testcontainers-go-monorepo branch from 90db5b3 to 40a9f92 Compare February 7, 2025 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants