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

[thomhurst]

This PR contains the following updates:

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

---

Release Notes

testcontainers/testcontainers-dotnet (Testcontainers.Kafka)

v4.7.0

Compare Source

What's Changed

This release doesn't introduce breaking changes to the public API, but it isn't binary compatible due to necessary internal changes. Make sure to update all related packages (Testcontainers modules) to the same version. See more details here. Thanks to all contributors 👏.

⚠️ Breaking Changes

• feat(Kafka): Add KRaft support (#​1353) @​SukharevAndrey
• feat: Add ability to override enumerable builder values (#​1506) @​HofmeisterAn

🚀 Features

• feat: Add wait strategy to check external (TCP) port availability (#​1495) @​WhiteTomX
• feat(Kafka): Add KRaft support (#​1353) @​SukharevAndrey
• feat: Relax Base64 auth provider and ignore path segments in Docker registry URLs (#​1516) @​HofmeisterAn
• feat: Add ability to override enumerable builder values (#​1506) @​HofmeisterAn
• feat(Elasticsearch): Return HTTP connection string if security is disabled (#​1494) @​HofmeisterAn
• fix: Add tooling to inherit XML docs (#​1493) @​HofmeisterAn
• feat: Resolve .slnx (solution) file in common directory paths (#​1492) @​alexander-jesner-AP
• feat: Support getting all mapped ports (#​1485) @​HofmeisterAn
• feat: Add named pipe connection timeout custom configuration (#​1480) @​HofmeisterAn

🐛 Bug Fixes

• feat(Kafka): Add KRaft support (#​1353) @​SukharevAndrey
• fix: Send valid HTTP test responses (#​1505) @​HofmeisterAn
• fix: Use null-conditional operator to access FinishedAt (#​1499) @​HofmeisterAn
• fix: Remove timeout that kills PID 1 when stopping a container (#​1481) @​HofmeisterAn
• fix(Pulsar): Wait until the consumer becomes connected (#​1467) @​HofmeisterAn
• fix(ServiceBus): Remove container lifecycle overrides (#​1465) @​HofmeisterAn

📖 Documentation

• docs: Explain how to substitute the Docker Hub registry (#​1503) @​HofmeisterAn
• docs: Extend example copying files to a container (#​1487) @​cimnine

🧹 Housekeeping

• chore: Change Kafka vendor configuration from class to interface (#​1519) @​HofmeisterAn
• chore: Bump Docker.DotNet version to 3.128.5 (#​1511) @​HofmeisterAn
• chore: Build a single project instead of the whole solution (#​1502) @​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

---

Reviewing Testcontainers.Kafka Dependency Update

Review Checklist:

• Read the changed file (Directory.Packages.props)
• Analyze release notes for breaking changes and compatibility issues
• Check for Kafka-related tests in the codebase
• Review security implications
• Assess performance impact
• Provide final recommendations

Analysis Complete ✅

Code Quality & Usage

• Location: Only used in example test project (TUnit.Example.Asp.Net.TestProject)
• Purpose: Demonstrates TUnit's test infrastructure orchestration with Docker containers
• Usage Pattern: Clean dependency injection pattern using TUnit's ClassDataSource attributes
• Code Quality: ✅ Well-structured, follows established patterns

Breaking Changes Assessment

⚠️ Important: Version 4.7.0 introduces binary compatibility breaks despite no public API changes:

• KRaft Support: Major new feature for Kafka containers (#1353)
• Builder Overrides: New ability to override enumerable builder values (#1506)
• Recommendation: Update all Testcontainers packages to 4.7.0 (currently PostgreSql and Redis are still on 4.6.0)

Security Concerns

✅ Low Risk:

• Release includes security-relevant fixes (Docker registry auth improvements, HTTP response validation)
• No known vulnerabilities introduced
• Test-only usage limits exposure surface

Performance Considerations

✅ Positive Impact:

• Timeout improvements for container lifecycle management
• Enhanced wait strategies for external port availability
• Better resource cleanup (removes PID 1 timeout issues)

Test Coverage Impact

✅ No Action Needed:

• Current usage is in example/demo code, not critical test paths
• The existing pattern (KafkaBuilder().WithNetwork().Build()) remains fully compatible
• New KRaft support is additive and doesn't affect existing ZooKeeper-based setups

Recommendations

1. ✅ Approve Update: This is a safe minor version bump with beneficial improvements
2. 🔄 Consistency: Consider updating other Testcontainers packages in Directory.Packages.props:
   • Testcontainers.PostgreSql (4.6.0 → 4.7.0)
   • Testcontainers.Redis (4.6.0 → 4.7.0)
3. 🧪 Test Verification: Run integration tests to confirm container startup behavior remains stable
4. 📝 Future Enhancement: The new KRaft support could be leveraged for faster Kafka startup times in tests

Summary

This is a safe dependency update with performance improvements and new features. The breaking changes are internal implementation details that don't affect the current usage patterns in TUnit's example project.

[claude]

Claude finished @thomhurst's task —— View job

---

Reviewing Testcontainers.Kafka Dependency Update

Review Checklist:

• Read the changed file (Directory.Packages.props)
• Analyze release notes for breaking changes and compatibility issues
• Check for Kafka-related tests in the codebase
• Review security implications
• Assess performance impact
• Provide final recommendations

Analysis Complete ✅

Code Quality & Usage

• Location: Only used in example test project (TUnit.Example.Asp.Net.TestProject)
• Purpose: Demonstrates TUnit's test infrastructure orchestration with Docker containers
• Usage Pattern: Clean dependency injection pattern using TUnit's ClassDataSource attributes
• Code Quality: ✅ Well-structured, follows established patterns

Breaking Changes Assessment

⚠️ Important: Version 4.7.0 introduces binary compatibility breaks despite no public API changes:

• KRaft Support: Major new feature for Kafka containers (#1353)
• Builder Overrides: New ability to override enumerable builder values (#1506)
• Recommendation: Update all Testcontainers packages to 4.7.0 (currently PostgreSql and Redis are still on 4.6.0)

Security Concerns

✅ Low Risk:

• Release includes security-relevant fixes (Docker registry auth improvements, HTTP response validation)
• No known vulnerabilities introduced
• Test-only usage limits exposure surface

Performance Considerations

✅ Positive Impact:

• Timeout improvements for container lifecycle management
• Enhanced wait strategies for external port availability
• Better resource cleanup (removes PID 1 timeout issues)

Test Coverage Impact

✅ No Action Needed:

• Current usage is in example/demo code, not critical test paths
• The existing pattern (KafkaBuilder().WithNetwork().Build()) remains fully compatible
• New KRaft support is additive and doesn't affect existing ZooKeeper-based setups

Recommendations

1. ✅ Approve Update: This is a safe minor version bump with beneficial improvements
2. 🔄 Consistency: Consider updating other Testcontainers packages in Directory.Packages.props:
   • Testcontainers.PostgreSql (4.6.0 → 4.7.0)
   • Testcontainers.Redis (4.6.0 → 4.7.0)
3. 🧪 Test Verification: Run integration tests to confirm container startup behavior remains stable
4. 📝 Future Enhancement: The new KRaft support could be leveraged for faster Kafka startup times in tests

Summary

This is a safe dependency update with performance improvements and new features. The breaking changes are internal implementation details that don't affect the current usage patterns in TUnit's example project.

---

[claude]

Claude finished @thomhurst's task —— View job

---

Reviewing Testcontainers.Kafka Dependency Update

Review Checklist:

• Read the changed file (Directory.Packages.props)
• Analyze release notes for breaking changes and compatibility issues
• Check for Kafka-related tests in the codebase
• Review security implications
• Assess performance impact
• Provide final recommendations

Analysis Complete ✅

Code Quality & Usage

• Location: Only used in example test project (TUnit.Example.Asp.Net.TestProject)
• Purpose: Demonstrates TUnit's test infrastructure orchestration with Docker containers
• Usage Pattern: Clean dependency injection pattern using TUnit's ClassDataSource attributes
• Code Quality: ✅ Well-structured, follows established patterns

Breaking Changes Assessment

⚠️ Important: Version 4.7.0 introduces binary compatibility breaks despite no public API changes:

• KRaft Support: Major new feature for Kafka containers (#1353)
• Builder Overrides: New ability to override enumerable builder values (#1506)
• Recommendation: Update all Testcontainers packages to 4.7.0 (currently PostgreSql is at 4.7.0, Redis is still at 4.6.0)

Security Concerns

✅ Low Risk:

• Release includes security-relevant fixes (Docker registry auth improvements, HTTP response validation)
• No known vulnerabilities introduced
• Test-only usage limits exposure surface

Performance Considerations

✅ Positive Impact:

• Timeout improvements for container lifecycle management
• Enhanced wait strategies for external port availability
• Better resource cleanup (removes PID 1 timeout issues)

Test Coverage Impact

✅ No Action Needed:

• Current usage is in example/demo code, not critical test paths
• The existing pattern (KafkaBuilder().WithNetwork().Build()) remains fully compatible
• New KRaft support is additive and doesn't affect existing ZooKeeper-based setups

Recommendations

1. ✅ Approve Update: This is a safe minor version bump with beneficial improvements
2. 🔄 Consistency: Consider updating other Testcontainers packages in Directory.Packages.props:
   • Testcontainers.Redis (4.6.0 → 4.7.0)
3. 🧪 Test Verification: Run integration tests to confirm container startup behavior remains stable
4. 📝 Future Enhancement: The new KRaft support could be leveraged for faster Kafka startup times in tests

Summary

This is a safe dependency update with performance improvements and new features. The breaking changes are internal implementation details that don't affect the current usage patterns in TUnit's example project.

---