Repository navigation
[gomod] Bump github.com/testcontainers/testcontainers-go from 0.44.0 to 0.45.0 - #96
Conversation
Bumps [github.com/testcontainers/testcontainers-go](https://github.com/testcontainers/testcontainers-go) from 0.44.0 to 0.45.0. - [Release notes](https://github.com/testcontainers/testcontainers-go/releases) - [Commits](testcontainers/testcontainers-go@v0.44.0...v0.45.0) --- updated-dependencies: - dependency-name: github.com/testcontainers/testcontainers-go dependency-version: 0.45.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![ecosquad-autoreview[bot]](https://avatars.githubusercontent.com/in/5135070?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary
Dependabot-style bump of github.com/testcontainers/testcontainers-go from v0.44.0 → v0.45.0, touching only go.mod and go.sum. No application source is changed. The v0.45.0 release notes call out breaking changes, but they are all scoped to the CockroachDB, Dex, and Cosmos DB example adapters (modules/*/examples) — none of which this repo imports. This repo only uses the modules/postgres module (tests/main_test.go), whose API (postgres.Run, WithInitScripts, WithDatabase, WithUsername, WithPassword, MappedPort, TerminateContainer, wait.ForLog) is unchanged. So the bump itself is safe for the code as written.
Findings
Warning — Inconsistent testcontainers version split (go.mod, lines 19–20)
github.com/testcontainers/testcontainers-go v0.45.0
github.com/testcontainers/testcontainers-go/modules/postgres v0.44.0
The core library was bumped to v0.45.0 but the directly-depended modules/postgres module was left at v0.44.0. The v0.45.0 release is cut as a single version across the whole repo ("chore: use new version (v0.45.0) in modules and examples"), so modules/postgres v0.45.0 exists and is the intended companion.
Why it matters:
- The two halves of the same testcontainers ecosystem are pinned to different releases. Go's MVS will build
modules/postgresv0.44.0 against core v0.45.0, which in practice compiles (the core API is backward compatible), but this is fragile and defeats the point of the bump — you're not actually on a coherent v0.45.0 stack. - A partial bump like this is easy to accidentally leave in place, and it muddies future "what version are we on" answers.
Fix: bump the module to match the core, i.e. change line 20 to
github.com/testcontainers/testcontainers-go/modules/postgres v0.45.0
and run go mod tidy to refresh go.sum.
Note — CI not yet green (build / go-test / go-test-acc still queued)
The build, go-test, go-test-acc, and ent-codegen jobs were still queued at review time (only GitGuardian is green and CodeQL is neutral/broken-config). Because the change is dependency-only, the real verification is that the test build compiles and the container-based suite passes. Please confirm these jobs go green before merging; if the version split above causes any compile friction, bumping modules/postgres to v0.45.0 should resolve it.
Verdict
No correctness, security, or data-loss issues — the change is test-only and the relevant postgres API is unchanged in v0.45.0. The only real concern is the inconsistent core/module version split, which is a consistency fix rather than a blocker. Approving with the recommendation to bump modules/postgres to v0.45.0.
Bumps github.com/testcontainers/testcontainers-go from 0.44.0 to 0.45.0.
Release notes
Sourced from github.com/testcontainers/testcontainers-go's releases.
... (truncated)
Commits
b4fe821chore: use new version (v0.45.0) in modules and examplesd40be72chore(deps): bump github.com/go-jose/go-jose/v4 in /modules/dex/examples (#4088)0d12cc6chore(modules): finish test client isolation and document examples modules (#...9cc89fdchore(modules): isolate eight remaining compatible client SDKs (#4086)9ec5407chore(modules)!: extract CockroachDB and Dex client adapters (#4087)5c9480fchore(modules): isolate client examples across eleven more modules (#4084)6aaef66fix(ci): initialize sbx network policy before tests (#4085)55f58fechore(modules): isolate client examples across eleven modules (#4083)ea5a2e8chore(deps): bump go.mongodb.org/mongo-driver (#4075)60b08c4docs: show cumulative clones and unique cloners (#4082)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)