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

[thomhurst]

This PR contains the following updates:

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

---

Release Notes

testcontainers/testcontainers-dotnet (Testcontainers.PostgreSql)

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

---

PR Review: Testcontainers.PostgreSql Update to 4.7.0

I've completed a comprehensive review of this dependency update PR.

Review Summary:

✅ Code Quality & Best Practices

• Changes are minimal and correctly applied to central package management files
• Follows the project's centralized versioning pattern in Directory.Packages.props
• Template project correctly updated to match

⚠️ Compatibility Concerns

CRITICAL: The release notes explicitly state this version "isn't binary compatible due to necessary internal changes" and recommend updating "all related packages (Testcontainers modules) to the same version."

Current version misalignment in Directory.Packages.props:

• Testcontainers.PostgreSql: 4.7.0 ✅ (this PR)
• Testcontainers.Kafka: 4.6.0 ❌ (needs update)
• Testcontainers.Redis: 4.6.0 ❌ (needs update)

🔍 Impact Analysis

Files using PostgreSQL containers:

• TUnit.Example.Asp.Net.TestProject/InMemoryPostgreSqlDatabase.cs:13 - Creates PostgreSQL containers
• TUnit.Example.Asp.Net.TestProject/WebApplicationFactory.cs:42 - Uses connection string
• Integration tests in Tests.cs depend on this infrastructure

🛡️ Security Assessment

• No security vulnerabilities introduced
• Update includes security-related fixes in the release notes
• Container configuration remains secure with proper credential handling

⚡ Performance Considerations

• Minor version update should not impact performance significantly
• Release includes various bug fixes that may improve stability
• Container startup/teardown performance should remain consistent

🧪 Test Coverage

• Existing integration tests in TUnit.Example.Asp.Net.TestProject provide coverage
• Tests use WebApplicationFactory which integrates all three container types
• Template projects include working examples

🚨 Recommendations

1. BLOCK MERGE until Kafka and Redis containers are updated to 4.7.0 to maintain compatibility
2. Update Testcontainers.Kafka from 4.6.0 → 4.7.0
3. Update Testcontainers.Redis from 4.6.0 → 4.7.0
4. Run integration tests to verify all containers work together after updates

✅ After Compatibility Fix

Once all Testcontainers packages are aligned to 4.7.0, this update should be safe to merge as it:

• Follows semantic versioning (minor update)
• Includes beneficial bug fixes and features
• Maintains existing API compatibility
• Has proper test coverage

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Testcontainers.PostgreSql Update to 4.7.0

I've completed a comprehensive review of this dependency update PR.

Review Summary:

✅ Code Quality & Best Practices

• Changes are minimal and correctly applied to central package management files
• Follows the project's centralized versioning pattern in Directory.Packages.props
• Template project correctly updated to match

⚠️ Compatibility Concerns

CRITICAL: The release notes explicitly state this version "isn't binary compatible due to necessary internal changes" and recommend updating "all related packages (Testcontainers modules) to the same version."

Current version misalignment in Directory.Packages.props:

• Testcontainers.PostgreSql: 4.7.0 ✅ (this PR)
• Testcontainers.Kafka: 4.6.0 ❌ (needs update)
• Testcontainers.Redis: 4.6.0 ❌ (needs update)

🔍 Impact Analysis

Files using PostgreSQL containers:

• TUnit.Example.Asp.Net.TestProject/InMemoryPostgreSqlDatabase.cs:13 - Creates PostgreSQL containers
• TUnit.Example.Asp.Net.TestProject/WebApplicationFactory.cs:42 - Uses connection string
• Integration tests in Tests.cs depend on this infrastructure

🛡️ Security Assessment

• No security vulnerabilities introduced
• Update includes security-related fixes in the release notes
• Container configuration remains secure with proper credential handling

⚡ Performance Considerations

• Minor version update should not impact performance significantly
• Release includes various bug fixes that may improve stability
• Container startup/teardown performance should remain consistent

🧪 Test Coverage

• Existing integration tests in TUnit.Example.Asp.Net.TestProject provide coverage
• Tests use WebApplicationFactory which integrates all three container types
• Template projects include working examples

🚨 Recommendations

1. BLOCK MERGE until Kafka and Redis containers are updated to 4.7.0 to maintain compatibility
2. Update Testcontainers.Kafka from 4.6.0 → 4.7.0
3. Update Testcontainers.Redis from 4.6.0 → 4.7.0
4. Run integration tests to verify all containers work together after updates

✅ After Compatibility Fix

Once all Testcontainers packages are aligned to 4.7.0, this update should be safe to merge as it:

• Follows semantic versioning (minor update)
• Includes beneficial bug fixes and features
• Maintains existing API compatibility
• Has proper test coverage

---