Bump the go group with 3 updates

[dependabot]

Bumps the go group with 3 updates: github.com/stretchr/testify, github.com/testcontainers/testcontainers-go and github.com/urfave/cli.

Updates github.com/stretchr/testify from 1.11.0 to 1.11.1

Release notes

Sourced from github.com/stretchr/testify's releases.

v1.11.1

This release fixes #1785 introduced in v1.11.0 where expected argument values implementing the stringer interface (String() string) with a method which mutates their value, when passed to mock.Mock.On (m.On("Method", <expected>).Return()) or actual argument values passed to mock.Mock.Called may no longer match one another where they previously did match. The behaviour prior to v1.11.0 where the stringer is always called is restored. Future testify releases may not call the stringer method at all in this case.

What's Changed

• Backport #1786 to release/1.11: mock: revert to pre-v1.11.0 argument matching behavior for mutating stringers by @​brackendawson in stretchr/testify#1788

Full Changelog: stretchr/testify@v1.11.0...v1.11.1

Commits

• 2a57335 Merge pull request #1788 from brackendawson/1785-backport-1.11
• af8c912 Backport #1786 to release/1.11
• See full diff in compare view

Updates github.com/testcontainers/testcontainers-go from 0.35.0 to 0.38.0

Release notes

Sourced from github.com/testcontainers/testcontainers-go's releases.

v0.38.0

What's Changed

⚠️ Breaking Changes

• chore!: do not wait for all the exposed ports to be ready (#3199) @​mdelapenya

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.

• feat!: add options when creating RawCommand (#3168) @​benja-M-1

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

• deps: update testcontainers/sshd image to 1.3.0 (#3220) @​mdelapenya

🚀 Features

• feat(couchbase): adding auth to couchbase initCluster functions to support container reuse (#3048) @​waroir20
• feat: support adding wait strategies as functional option (#3161) @​mdelapenya
• feat: add more functional options for customising containers (#3156) @​mdelapenya
• feat(memcached): add memcached module (#3132) @​mdelapenya
• feat(valkey): add TLS support for Valkey (#3131) @​mdelapenya

🐛 Bug Fixes

• fix: strip headers from logs using log stream specification (#3226) @​LaurentGoderre
• fix: use PortEndpoint() in a few more modules (#3209) @​ash2k
• fix: docker container log consumer race (#3210) @​stevenh
• fix: use PortEndpoint() in a few more modules (#3207) @​ash2k
• fix: use PortEndpoint() in a few more modules (#3206) @​ash2k
• fix: use PortEndpoint() in a few more modules (#3203) @​ash2k
• fix: try to fix more IPv6 handling issues (#3198) @​ash2k
• fix: workaround for moby/moby#50133 when reusing container (#3197) @​mabrarov
• feat(kafka,redpanda): support for waiting for mapped ports without external checks (#3165) @​mabrarov
• fix(etcd): expose ports for the etcd nodes (#3162) @​mdelapenya

... (truncated)

Commits

• 41bd601 chore: use new version (v0.38.0) in modules and examples
• a771fee Update go.mod in azure module (#3231)
• 7f916ae fix: strip headers from logs using log stream specification (#3226)
• 295ba91 chore: clarify image auth warning message for public images (#3228)
• ea392e9 chore(deps): bump github.com/go-viper/mapstructure/v2 (#3219)
• 122a4e5 chore(deps): bump github/codeql-action from 3.28.16 to 3.29.2 (#3222)
• 930caf5 chore(deps): bump mkdocs-include-markdown-plugin from 7.1.5 to 7.1.6 (#3225)
• 8a7416a deps: update testcontainers/sshd image to 1.3.0 (#3220)
• c6cd357 chore(deps): bump urllib3 from 2.2.2 to 2.5.0 (#3214)
• 4aa742c deps: gopsutil and purego update (#3217)
• Additional commits viewable in compare view

Updates github.com/urfave/cli from 1.22.16 to 1.22.17

Release notes

Sourced from github.com/urfave/cli's releases.

v1.22.17

What's Changed

• Update dependencies in v1 series by @​meatballhat in urfave/cli#2158

Full Changelog: urfave/cli@v1.22.16...v1.22.17

Commits

• 992e53d Merge pull request #2158 from urfave/v1-deps-up
• b37456c Update dependencies in v1 series
• 394fbd8 Merge pull request #2156 from urfave/v1-not-dependabot
• 2a5bdc7 Dependabot does not work like this
• 77bb234 Merge pull request #2153 from urfave/v1-dependabot-maybe
• 5d6ed14 Is this file needed on each release branch?
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.