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

[thomhurst]

This PR contains the following updates:

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

---

Release Notes

testcontainers/testcontainers-dotnet (Testcontainers.Redis)

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.Redis 4.8.0 Update

Review Checklist:

• Analyze the changed file
• Search for Testcontainers.Redis usage in codebase
• Review breaking changes impact
• Assess security and performance implications
• Provide comprehensive review feedback

---

🔍 Review Summary

This is a straightforward dependency update with minimal risk to the TUnit codebase. The update appears safe to merge.

📋 Detailed Analysis

Code Quality & Best Practices ✅

• Clean update: Single line change in Directory.Packages.props:80 updating version from 4.7.0 to 4.8.0
• Centralized dependency management: Properly using Directory.Packages.props for version management
• Consistent versioning: Kafka testcontainer already updated to 4.8.0, maintaining version alignment

Potential Issues & Compatibility ✅

Low Risk: The TUnit codebase has minimal exposure to breaking changes:

• Current Usage: InMemoryRedis.cs:14-16 uses only basic RedisBuilder().WithNetwork().Build() pattern
• Breaking Changes Analysis:
  • ❌ Reuse hash changes: Not applicable (TUnit doesn't appear to use container reuse)
  • ❌ WithResourceMapping/CopyAsync uid/gid params: Not used in TUnit codebase
  • ❌ Startup callback overloads: Not used in TUnit codebase
  • ❌ IContainerBuilder generic constraints: Not implementing custom builders

Performance Considerations ✅

• Positive impact: Wait strategies now default to Running mode with better error handling
• Improved reliability: ContainerNotRunningException will provide better debugging info
• No performance regression expected: TUnit's simple Redis usage pattern unaffected

Security Assessment ✅

• Dependency source: Official Testcontainers.Redis package from trusted maintainer
• No security vulnerabilities: No CVEs mentioned in release notes
• Improved error handling: Better container failure detection reduces potential issues

Test Coverage ✅

• Existing tests should pass: No API changes affecting InMemoryRedis class
• Test reliability may improve: Better wait strategy behavior and error reporting
• Recommendation: Run existing tests to verify container startup behavior

🚀 Recommendation

APPROVE - This update is safe to merge:

1. Zero breaking changes affect TUnit's usage patterns
2. Improved reliability with better error handling
3. Consistent dependency versions across testcontainer packages
4. Standard Renovate dependency update with proper release notes

🔧 Post-Merge Actions

• Monitor test runs for any unexpected Redis container behavior
• No code changes required in TUnit codebase

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Testcontainers.Redis 4.8.0 Update

Review Checklist:

• Analyze the changed file
• Search for Testcontainers.Redis usage in codebase
• Review breaking changes impact
• Assess security and performance implications
• Provide comprehensive review feedback

---

🔍 Review Summary

This is a straightforward dependency update with minimal risk to the TUnit codebase. The update appears safe to merge.

📋 Detailed Analysis

Code Quality & Best Practices ✅

• Clean update: Single line change in Directory.Packages.props:80 updating version from 4.7.0 to 4.8.0
• Centralized dependency management: Properly using Directory.Packages.props for version management
• Consistent versioning: Kafka testcontainer already updated to 4.8.0, maintaining version alignment

Potential Issues & Compatibility ✅

Low Risk: The TUnit codebase has minimal exposure to breaking changes:

• Current Usage: InMemoryRedis.cs:14-16 uses only basic RedisBuilder().WithNetwork().Build() pattern
• Breaking Changes Analysis:
  • ❌ Reuse hash changes: Not applicable (TUnit doesn't appear to use container reuse)
  • ❌ WithResourceMapping/CopyAsync uid/gid params: Not used in TUnit codebase
  • ❌ Startup callback overloads: Not used in TUnit codebase
  • ❌ IContainerBuilder generic constraints: Not implementing custom builders

Performance Considerations ✅

• Positive impact: Wait strategies now default to Running mode with better error handling
• Improved reliability: ContainerNotRunningException will provide better debugging info
• No performance regression expected: TUnit's simple Redis usage pattern unaffected

Security Assessment ✅

• Dependency source: Official Testcontainers.Redis package from trusted maintainer
• No security vulnerabilities: No CVEs mentioned in release notes
• Improved error handling: Better container failure detection reduces potential issues

Test Coverage ✅

• Existing tests should pass: No API changes affecting InMemoryRedis class
• Test reliability may improve: Better wait strategy behavior and error reporting
• Recommendation: Run existing tests to verify container startup behavior

🚀 Recommendation

APPROVE - This update is safe to merge:

1. Zero breaking changes affect TUnit's usage patterns
2. Improved reliability with better error handling
3. Consistent dependency versions across testcontainer packages
4. Standard Renovate dependency update with proper release notes

🔧 Post-Merge Actions

• Monitor test runs for any unexpected Redis container behavior
• No code changes required in TUnit codebase

---