chore(deps): update dependency testcontainers.kafka to 4.8.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Testcontainers.Kafka (source)	nuget	minor	4.7.0 -> 4.8.0

---

Release Notes

testcontainers/testcontainers-dotnet (Testcontainers.Kafka)

v4.8.0

Compare Source

What's Changed

Thank you to all the contributors 🙌.

In version 4.7.0, we noticed that the reuse hash could change depending on the order of dictionary values. This has been fixed to ensure that dictionary values are processed in a consistent order when generating the reuse hash. As a result, the reuse hash will likely change again with 4.8.0.

Wait strategies now default to the Running mode. This mode expects the container to remain running throughout startup. If the container exits unexpectedly, Testcontainers will throw a ContainerNotRunningException that includes the exit code and container logs.

The container startup callback now includes an additional overload that provides the actual container configuration. If you implement IContainerBuilder<TBuilderEntity, TContainerEntity>, you need to add the container configuration (e.g., IContainerConfiguration) as a third generic type constraint to IContainerBuilder.

IContainerBuilder.WithResourceMapping and IContainer.CopyAsync now include two new optional arguments: uid and gid. If you do not need to specify those, use named arguments for the existing parameters: fileMode or ct.

⚠️ Breaking Changes

• fix: Generate consistent reuse hashes by sorting dictionary keys (#​1554) @​0xced
• feat: Throw if container not running (#​1550) @​HofmeisterAn
• feat: Add startup callback overload with configuration type (#​1547) @​HofmeisterAn
• feat: Support UID/GID when copying files (#​1531) @​HofmeisterAn

🚀 Features

• feat: Throw if container not running (#​1550) @​HofmeisterAn
• feat: Add startup callback overload with configuration type (#​1547) @​HofmeisterAn
• feat: Add Docker build context (#​1536) @​HofmeisterAn
• feat: Add WithTarget(string) to image builder (#​1534) @​HofmeisterAn
• feat: Resolve Dockerfile ARGs pulling base images (#​1532) @​HofmeisterAn
• feat: Support UID/GID when copying files (#​1531) @​HofmeisterAn
• feat(Keycloak): Add API to import a realm configuration file (#​1526) @​VladislavAntonyuk

🐛 Bug Fixes

• fix: Generate consistent reuse hashes by sorting dictionary keys (#​1554) @​0xced
• fix(MongoDb): Use db.runCommand({hello:1}) do detect readiness (#​1548) @​HofmeisterAn
• fix(Papercut): Pin version 7.0 and set new HTTP and SMTP ports (#​1549) @​HofmeisterAn
• fix(Pulsar): Wait for default namespace (#​1539) @​HofmeisterAn
• fix(Keycloak): Wait until user created (#​1535) @​HofmeisterAn

📖 Documentation

• docs: Remove obsolete UntilOperationIsSucceeded wait strategy example (#​1551) @​ascott18
• docs: Fix link to Ryuk in IContainerBuilder.WithAutoRemove code comment (#​1546) @​hojmark

🧹 Housekeeping

• chore: Don't create a static field in a generic class (#​1555) @​HofmeisterAn
• chore: Add test certificates to common project (#​1545) @​HofmeisterAn
• chore: Update CI workflow to ubuntu-24.04 (#​1544) @​HofmeisterAn
• chore: Collect test projects at CI runtime (#​1543) @​HofmeisterAn
• chore: Fix grammar (#​1542) @​Smoothengineer
• chore: Bump Ryuk (#​1537) @​HofmeisterAn
• chore: Remove obsolete wait strategy: UntilPortIsAvailable(int) (#​1528) @​HofmeisterAn
• feat: Prepare next release cycle (4.8.0) (#​1523) @​HofmeisterAn

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.

---

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

---

This PR has been generated by Renovate Bot.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Testcontainers.Kafka 4.7.0 → 4.8.0

Review Tasks:

• Examine the package change in Directory.Packages.props
• Search for Testcontainers usage in TUnit codebase
• Analyze breaking changes impact
• Review security implications
• Assess performance considerations
• Check test coverage implications
• Provide final recommendations

---

Code Quality and Best Practices ✅

The dependency update itself is clean and follows the centralized package management pattern using Directory.Packages.props. The change is minimal and correctly updates only the Testcontainers.Kafka version.

Potential Bugs or Issues ⚠️

Breaking Changes Impact:

1. Wait Strategy Changes: The release notes indicate wait strategies now default to "Running" mode, which throws ContainerNotRunningException if containers exit unexpectedly.

   • Impact on TUnit: Found usage in KafkaUI.cs:23 with custom wait strategy UntilMessageIsLogged(".*Started KafkaUiApplication.*"). This should continue working but may have different error handling behavior.

2. Reuse Hash Changes: The reuse hash generation has been made consistent, which will likely break existing container reuse setups.

   • Impact on TUnit: May cause containers to be recreated instead of reused, potentially increasing test execution time on first run after upgrade.

3. API Changes: New parameters added to WithResourceMapping and CopyAsync methods (uid/gid).

   • Impact on TUnit: Current code doesn't use these methods, so no breaking changes detected.

4. Startup Callback Changes: New overload requiring configuration type parameter.

   • Impact on TUnit: No startup callbacks found in current usage, so no impact.

Security Concerns ✅

• The update includes security improvements through better container lifecycle management
• No security vulnerabilities introduced by the dependency update
• Container isolation and cleanup remain robust

Performance Considerations ⚠️

• Positive: Better container lifecycle management may improve resource cleanup
• Negative: Hash changes will invalidate container reuse on first run, causing slower initial test execution
• The "Running" mode wait strategy may provide faster failure detection for problematic containers

Test Coverage ✅

Current Testcontainers usage in TUnit is primarily in example/demo projects:

• TUnit.Example.Asp.Net.TestProject - Kafka, PostgreSQL, Redis containers
• Usage patterns are simple and should remain compatible
• No complex scenarios that would be affected by the breaking changes

Recommendations

✅ APPROVE - This is a low-risk dependency update with the following considerations:

1. Expected Behavior Changes:

   • Container reuse will be broken on first run (containers will be recreated)
   • More aggressive container failure detection due to "Running" mode wait strategies

2. Monitor After Merge:

   • Watch for increased test execution time on first CI run
   • Verify no unexpected container exit failures in integration tests

3. Future Considerations:

   • If using container reuse extensively, the hash change is a one-time impact
   • The improved error handling should provide better debugging for container issues

The codebase uses Testcontainers in a straightforward manner without relying on the affected advanced features. The breaking changes primarily impact complex container orchestration scenarios not present in TUnit's current usage.

---