chore(deps): update dependency testcontainers.kafka to 4.12.0#5962
Conversation
There was a problem hiding this comment.
Dependency Update Review: Testcontainers.Kafka 4.11.0 → 4.12.0
This is a straightforward Renovate-managed dependency bump. The diff is minimal (one line in Directory.Packages.props), but there is one thing worth noting from the upstream release notes.
⚠️ Breaking Change in Upstream: Docker.DotNet 3.131.1 → 4.0.2
The 4.12.0 release notes call out a breaking change due to bumping Docker.DotNet from 3.131.1 to 4.0.2. Since Testcontainers.Kafka takes this as a transitive dependency, any code that directly references Docker.DotNet types (e.g., CreateContainerParameters, HostConfig, etc.) could break at compile time.
A quick check shows TUnit's Kafka usage is limited to TUnit.Example.Asp.Net.TestProject (e.g., KafkaUI.cs, InMemoryKafka.cs), which is an example/integration project rather than the core engine — so the blast radius is contained. The pending CI runs (integration-tests, modularpipeline) will be the definitive signal here.
Version Drift Across Testcontainers Modules
After this PR, the package versions will be:
Testcontainers.Kafka: 4.12.0Testcontainers.PostgreSql: 4.11.0Testcontainers.Redis: 4.11.0
Each module is versioned independently upstream so this is intentional, but it means the three modules may carry different transitive Docker.DotNet versions. In practice this is fine as long as the resolved transitive dependency is the highest version — but it's worth being aware of in case a future incompatibility surfaces.
Summary
The change is clean and correct. The breaking-change flag in the release notes is the main thing to watch, and the integration-test CI run will confirm whether anything is affected. No changes needed from my side — approve once CI is green.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
f63f58f to
651768e
Compare
There was a problem hiding this comment.
Review Update: Testcontainers.Kafka 4.11.0 → 4.12.0
Building on the previous review:
Previous Concerns — Status
Docker.DotNet bump (3.131.1 → 4.0.2) remains unresolved until those runs complete. Given TUnit's Kafka usage is confined to the example/integration project rather than core engine code, a compile-time break is possible but the blast radius is narrow.
Version drift (Kafka 4.12.0 vs PostgreSql/Redis 4.11.0): Still present after this PR — no action needed, but worth noting for future consolidated upgrades.
Change Itself
The one-line diff in Directory.Packages.props is correct and minimal. Nothing else needs updating for a Renovate-managed version pin change.
Recommendation
This is safe to merge once CI is green, especially given auto-merge is already enabled. The Snyk security check passed with no manifest concerns. No code changes required.
This PR contains the following updates:
4.11.0→4.12.0Release Notes
testcontainers/testcontainers-dotnet (Testcontainers.Kafka)
v4.12.0Compare Source
What's Changed
Thanks to all contributors 👏.
🚀 Features
🐛 Bug Fixes
📖 Documentation
🧹 Housekeeping
📦 Dependency Updates
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ 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 this update again.
This PR has been generated by Mend Renovate.