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

[thomhurst]

This PR contains the following updates:

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

---

Release Notes

testcontainers/testcontainers-dotnet (Testcontainers.PostgreSql)

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.PostgreSql Dependency Update

Reviewing the dependency update from Testcontainers.PostgreSql 4.7.0 → 4.8.0

Tasks:

• Read repository guidelines (CLAUDE.md)
• Examine changed files
• Search for Testcontainers.PostgreSql usage in codebase
• Analyze breaking changes impact
• Provide comprehensive review feedback

---

✅ Code Quality and Best Practices

The changes are minimal and well-scoped:

• Directory.Packages.props:79: Updates version from 4.7.0 to 4.8.0
• Template file: Updates the Aspire starter template to use the new version

The centralized package management approach is excellent and the change is consistent across all references.

⚠️ Breaking Changes Analysis

The release notes indicate several breaking changes in Testcontainers 4.8.0:

1. Reuse Hash Changes: The hash generation now sorts dictionary keys consistently, which may affect container reuse behavior
2. Wait Strategy Defaults: Now defaults to Running mode and throws ContainerNotRunningException if containers exit unexpectedly
3. API Signature Changes:
   • IContainerBuilder.WithResourceMapping now has optional uid/gid parameters
   • IContainer.CopyAsync has new optional parameters
   • Container startup callbacks have new overloads

🔍 Impact Assessment on TUnit Codebase

Current Usage Analysis:

• InMemoryPostgreSqlDatabase.cs:13-18: Uses basic PostgreSqlBuilder with standard configuration - ✅ No impact expected
• Playground/Program.cs:38: Simple PostgreSqlBuilder usage - ✅ No impact expected
• KafkaUI.cs:23: Uses custom wait strategy with UntilMessageIsLogged - ✅ Should work fine

Good News: The TUnit codebase uses only basic PostgreSQL container functionality without any of the APIs affected by breaking changes.

🚀 Performance Considerations

• Positive: The hash consistency fix should improve container reuse reliability
• Neutral: No performance regressions expected from the changes
• Note: The new Running wait strategy mode may provide better error reporting when containers fail

🔒 Security Concerns

None identified. This is a standard dependency update from a trusted source with no security-related changes.

🧪 Test Coverage

Recommendation: While no code changes are needed, consider:

1. Running the existing PostgreSQL integration tests to verify compatibility
2. Testing the container startup behavior with the new wait strategy defaults

The existing test coverage in TUnit.Example.Asp.Net.TestProject should validate the upgrade works correctly.

📝 Summary

✅ APPROVED - This is a safe dependency update with no breaking impact on the TUnit codebase.

Key Points:

• Breaking changes don't affect TUnit's usage patterns
• All current PostgreSQL container usage will continue to work
• The upgrade brings improvements in container reuse reliability and error reporting
• No code changes required

Recommendation: Merge this PR and monitor the integration tests to ensure container behavior remains stable.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Testcontainers.PostgreSql Dependency Update

Reviewing the dependency update from Testcontainers.PostgreSql 4.7.0 → 4.8.0

Tasks:

• Read repository guidelines (CLAUDE.md)
• Examine changed files
• Search for Testcontainers.PostgreSql usage in codebase
• Analyze breaking changes impact
• Provide comprehensive review feedback

---

✅ Code Quality and Best Practices

The changes are minimal and well-scoped:

• Directory.Packages.props:79: Updates version from 4.7.0 to 4.8.0
• Template file: Updates the Aspire starter template to use the new version

The centralized package management approach is excellent and the change is consistent across all references.

⚠️ Breaking Changes Analysis

The release notes indicate several breaking changes in Testcontainers 4.8.0:

1. Reuse Hash Changes: The hash generation now sorts dictionary keys consistently, which may affect container reuse behavior
2. Wait Strategy Defaults: Now defaults to Running mode and throws ContainerNotRunningException if containers exit unexpectedly
3. API Signature Changes:
   • IContainerBuilder.WithResourceMapping now has optional uid/gid parameters
   • IContainer.CopyAsync has new optional parameters
   • Container startup callbacks have new overloads

🔍 Impact Assessment on TUnit Codebase

Current Usage Analysis:

• InMemoryPostgreSqlDatabase.cs:13-18: Uses basic PostgreSqlBuilder with standard configuration - ✅ No impact expected
• Playground/Program.cs:38: Simple PostgreSqlBuilder usage - ✅ No impact expected
• KafkaUI.cs:23: Uses custom wait strategy with UntilMessageIsLogged - ✅ Should work fine

Good News: The TUnit codebase uses only basic PostgreSQL container functionality without any of the APIs affected by breaking changes.

🚀 Performance Considerations

• Positive: The hash consistency fix should improve container reuse reliability
• Neutral: No performance regressions expected from the changes
• Note: The new Running wait strategy mode may provide better error reporting when containers fail

🔒 Security Concerns

None identified. This is a standard dependency update from a trusted source with no security-related changes.

🧪 Test Coverage

Recommendation: While no code changes are needed, consider:

1. Running the existing PostgreSQL integration tests to verify compatibility
2. Testing the container startup behavior with the new wait strategy defaults

The existing test coverage in TUnit.Example.Asp.Net.TestProject should validate the upgrade works correctly.

📝 Summary

✅ APPROVED - This is a safe dependency update with no breaking impact on the TUnit codebase.

Key Points:

• Breaking changes don't affect TUnit's usage patterns
• All current PostgreSQL container usage will continue to work
• The upgrade brings improvements in container reuse reliability and error reporting
• No code changes required

Recommendation: Merge this PR and monitor the integration tests to ensure container behavior remains stable.

---