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

[thomhurst]

This PR contains the following updates:

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

---

Release Notes

testcontainers/testcontainers-dotnet (Testcontainers.Redis)

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

---

Code Review: Testcontainers.Redis 4.7.0 Update

Review Checklist:

• Read changed files and understand the update
• Search for Redis usage in codebase
• Analyze release notes for breaking changes
• Check test coverage and compatibility
• Provide comprehensive review feedback

Analysis Summary:

Package Changes:

• Testcontainers.Redis updated from 4.6.0 → 4.7.0 in Directory.Packages.props:83
• Note: Testcontainers.Kafka and Testcontainers.PostgreSql remain at 4.6.0 (version inconsistency)

Redis Usage in Codebase:

1. TUnit.Example.Asp.Net.TestProject/InMemoryRedis.cs: Uses RedisContainer and RedisBuilder from Testcontainers.Redis
2. TUnit.TestProject/ParallelPropertyInjectionTests.cs: Contains mock RedisContainer classes for testing parallel initialization (not actual Testcontainers)
3. Documentation examples: Multiple docs reference Redis containers for testing scenarios

Potential Issues & Concerns:

🚨 Critical - Version Incompatibility:
The release notes explicitly state: "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."

Current versions:

• Testcontainers.Kafka: 4.6.0 ❌
• Testcontainers.PostgreSql: 4.6.0 ❌
• Testcontainers.Redis: 4.7.0 ✅

This will cause binary compatibility issues as different Testcontainers modules are on different versions.

Recommendations:

🔧 Required Actions:

1. Update all Testcontainers packages to 4.7.0 to maintain binary compatibility:

   <PackageVersion Include="Testcontainers.Kafka" Version="4.7.0" />
   <PackageVersion Include="Testcontainers.PostgreSql" Version="4.7.0" />
   <PackageVersion Include="Testcontainers.Redis" Version="4.7.0" />

2. Test the example projects that use Redis containers, particularly:

   • TUnit.Example.Asp.Net.TestProject
   • Any integration tests using the InMemoryRedis class

⚠️ Breaking Changes Assessment:

• KRaft support for Kafka: May affect Kafka usage if present
• Ability to override enumerable builder values: Low impact
• Bug fixes: Generally positive, especially the timeout fix for PID 1 when stopping containers

🔒 Security & Performance:

• ✅ No security concerns identified
• ✅ Performance improvements from bug fixes (container stop timeout removal)
• ✅ Enhanced functionality with external TCP port availability checks

📋 Test Coverage:

• The existing InMemoryRedis.cs implementation should be tested after version alignment
• Mock Redis classes in test files are unaffected (they don't use actual Testcontainers)

Verdict:

❌ This PR should not be merged as-is due to binary compatibility issues. All Testcontainers packages must be updated to the same version (4.7.0) simultaneously.

---

[claude]

Claude finished @thomhurst's task —— View job

---

Code Review: Testcontainers.Redis 4.7.0 Update

Review Checklist:

• Read changed files and understand the update
• Search for Redis usage in codebase
• Analyze release notes for breaking changes
• Check test coverage and compatibility
• Provide comprehensive review feedback

---

🚨 CRITICAL ISSUE: Binary Compatibility Violation

This PR should NOT be merged as-is due to a binary compatibility issue explicitly mentioned in the Testcontainers 4.7.0 release notes.

Problem Analysis

Version Inconsistency in Directory.Packages.props:

<PackageVersion Include="Testcontainers.Kafka" Version="4.6.0" />          
<PackageVersion Include="Testcontainers.PostgreSql" Version="4.6.0" />       
<PackageVersion Include="Testcontainers.Redis" Version="4.7.0" />          

Release Notes Warning (4.7.0):

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

Impact Assessment

🔍 Code Quality & Best Practices

• ❌ Version Management: Mixing Testcontainers package versions violates dependency management best practices
• ✅ Code Structure: Existing Redis implementations follow proper patterns with IAsyncInitializer and IAsyncDisposable
• ✅ Resource Management: Proper container lifecycle management in place

🐛 Potential Bugs & Issues

High Risk Issues:

1. Binary Compatibility Failures: Different Testcontainers versions may cause runtime exceptions in InMemoryRedis.cs:14, InMemoryKafka.cs:15, and InMemoryPostgreSqlDatabase.cs:13
2. Integration Test Failures: The WebApplicationFactory.cs uses all three container types together - version mismatches could cause test instability
3. Docker Network Issues: Shared DockerNetwork dependency across different container versions may cause networking problems

Evidence from Codebase:

• InMemoryRedis.cs:2: Imports both Testcontainers.PostgreSql and Testcontainers.Redis - version mismatch risk
• WebApplicationFactory.cs:18-22: Uses Redis, Kafka, and PostgreSQL containers together in a single test factory
• InMemoryKafka.cs:2-4: Imports all three Testcontainers packages with mixed versions

⚡ Performance Considerations

• ✅ Container Performance: 4.7.0 includes bug fixes that improve container stop timeout behavior
• ✅ Parallel Initialization: Existing parallel container startup patterns are preserved
• ❓ Unknown Impact: Binary incompatibility could cause unexpected performance degradation

🔒 Security Concerns

• ✅ No Direct Security Issues: The version update doesn't introduce security vulnerabilities
• ⚠️ Stability Risk: Binary compatibility issues could lead to unpredictable behavior in production

🧪 Test Coverage

Affected Test Areas:

1. TUnit.Example.Asp.Net.TestProject: Integration tests using all three container types
2. ParallelPropertyInjectionTests.cs: Mock containers (unaffected by version changes)
3. Playground/Program.cs: Redis container usage for development testing

Test Risks:

• Integration tests may fail intermittently due to binary compatibility issues
• Container initialization race conditions could become more pronounced
• Docker network communication between different container versions may fail

📋 Required Actions

🔧 Immediate Fix Required

<PackageVersion Include="Testcontainers.Kafka" Version="4.7.0" />
<PackageVersion Include="Testcontainers.PostgreSql" Version="4.7.0" />  
<PackageVersion Include="Testcontainers.Redis" Version="4.7.0" />

🧪 Testing Recommendations

1. Run Integration Tests: Verify TUnit.Example.Asp.Net.TestProject tests pass
2. Test Container Interactions: Ensure Redis, Kafka, and PostgreSQL containers work together
3. Validate Docker Networks: Confirm shared network functionality remains intact
4. Performance Baseline: Monitor container startup times for regressions

🔍 Monitoring Points

• Watch for container initialization failures in logs
• Monitor test flakiness after the update
• Check for any Docker network connectivity issues

Verdict: ❌ Changes Required

This PR cannot be merged safely until all Testcontainers packages are updated to version 4.7.0 simultaneously. The current approach violates the explicit compatibility requirements and creates significant risk of runtime failures in the test suite.

Recommended Approach:

1. Update all three Testcontainers packages to 4.7.0 in a single commit
2. Run the full test suite to validate compatibility
3. Monitor for any container-related test failures

---

[claude]

Claude finished @thomhurst's task —— View job

---

Code Review: Testcontainers.Redis 4.7.0 Update

Review Checklist:

• Read changed files and understand the update
• Search for Redis usage in codebase
• Analyze release notes for breaking changes
• Check test coverage and compatibility
• Provide comprehensive review feedback

---

🚨 CRITICAL ISSUE: Binary Compatibility Violation

This PR should NOT be merged as-is due to a binary compatibility issue explicitly mentioned in the Testcontainers 4.7.0 release notes.

Problem Analysis

Version Inconsistency in Directory.Packages.props:

<PackageVersion Include="Testcontainers.Kafka" Version="4.6.0" />          ❌
<PackageVersion Include="Testcontainers.PostgreSql" Version="4.7.0" />     ✅
<PackageVersion Include="Testcontainers.Redis" Version="4.7.0" />          ✅

Release Notes Warning (4.7.0):

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

Impact Assessment

🔍 Code Quality & Best Practices

• ❌ Version Management: Mixing Testcontainers package versions violates dependency management best practices
• ✅ Code Structure: Existing Redis implementations follow proper patterns with IAsyncInitializer and IAsyncDisposable
• ✅ Resource Management: Proper container lifecycle management in place

🐛 Potential Bugs & Issues

High Risk Issues:

1. Binary Compatibility Failures: Different Testcontainers versions may cause runtime exceptions in InMemoryRedis.cs:14, InMemoryKafka.cs:15, and InMemoryPostgreSqlDatabase.cs:13
2. Integration Test Failures: The WebApplicationFactory.cs uses all three container types together - version mismatches could cause test instability
3. Docker Network Issues: Shared DockerNetwork dependency across different container versions may cause networking problems

Evidence from Codebase:

• InMemoryRedis.cs:2: Imports both Testcontainers.PostgreSql and Testcontainers.Redis - version mismatch risk
• WebApplicationFactory.cs:18-22: Uses Redis, Kafka, and PostgreSQL containers together in a single test factory
• InMemoryKafka.cs:2-4: Imports all three Testcontainers packages with mixed versions

⚡ Performance Considerations

• ✅ Container Performance: 4.7.0 includes bug fixes that improve container stop timeout behavior
• ✅ Parallel Initialization: Existing parallel container startup patterns are preserved
• ❓ Unknown Impact: Binary incompatibility could cause unexpected performance degradation

🔒 Security Concerns

• ✅ No Direct Security Issues: The version update doesn't introduce security vulnerabilities
• ⚠️ Stability Risk: Binary compatibility issues could lead to unpredictable behavior in production

🧪 Test Coverage

Affected Test Areas:

1. TUnit.Example.Asp.Net.TestProject: Integration tests using all three container types
2. ParallelPropertyInjectionTests.cs: Mock containers (unaffected by version changes)
3. Playground/Program.cs: Redis container usage for development testing

Test Risks:

• Integration tests may fail intermittently due to binary compatibility issues
• Container initialization race conditions could become more pronounced
• Docker network communication between different container versions may fail

📋 Required Actions

🔧 Immediate Fix Required

<PackageVersion Include="Testcontainers.Kafka" Version="4.7.0" />
<PackageVersion Include="Testcontainers.PostgreSql" Version="4.7.0" />  
<PackageVersion Include="Testcontainers.Redis" Version="4.7.0" />

🧪 Testing Recommendations

1. Run Integration Tests: Verify TUnit.Example.Asp.Net.TestProject tests pass
2. Test Container Interactions: Ensure Redis, Kafka, and PostgreSQL containers work together
3. Validate Docker Networks: Confirm shared network functionality remains intact
4. Performance Baseline: Monitor container startup times for regressions

🔍 Monitoring Points

• Watch for container initialization failures in logs
• Monitor test flakiness after the update
• Check for any Docker network connectivity issues

Verdict: ❌ Changes Required

This PR cannot be merged safely until all Testcontainers packages are updated to version 4.7.0 simultaneously. The current approach violates the explicit compatibility requirements and creates significant risk of runtime failures in the test suite.

Recommended Approach:

1. Update all three Testcontainers packages to 4.7.0 in a single commit
2. Run the full test suite to validate compatibility
3. Monitor for any container-related test failures

---