test(infra): pin Postgres test image to 17-alpine for prod parity#6
Merged
Conversation
.env.test ran postgres:16-alpine while the production compose stack runs Postgres 17 (per CLAUDE.md stack pins). Bumping the test image closes the parity gap so Testcontainers boot the same major Postgres the deployed REST + Services exercise — same migrations, same dialect, same JSONB / EF Core 10 surface. Verified end-to-end: ./build.sh IntegrationTests -> SetupTestcontainers / Restore / Compile / IntegrationTests all succeeded. This closes task #6. The rest of the test infrastructure was already OrbStack-backed: - Docker context defaults to orbstack (`docker context ls` -> orbstack *). - Every */Tests/Integration/ fixture spins real containers via Testcontainers (Postgres / RabbitMQ / MinIO / Elasticsearch). - The only intentional fake is FakeTextSummarizer (Gemini is third-party and out of scope for local containers — documented in CLAUDE.md gotchas). - The remaining Fake*.cs files are FakeLoggerExtensions wrappers around Microsoft.Extensions.Diagnostics.Testing.FakeLogger — not a real-deps concern. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the integration test environment’s Postgres container image to match the production stack’s major version, reducing version skew between local/CI integration tests and the deployed compose environment.
Changes:
- Pin
POSTGRES_IMAGEin.env.testfrompostgres:16-alpinetopostgres:17-alpine. - Expand the
.env.testcontainer image comment to describe the production-parity intent for test infrastructure.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+18
to
+20
| # MinIO latest, Elasticsearch 9.x). Bumping postgres 16 -> 17 closes the parity | ||
| # gap with the production compose stack so integration tests exercise the same | ||
| # migration / dialect surface the deployed REST + Services see. |
| # Container images — pinned to match production majors (Postgres 17, RabbitMQ 4, | ||
| # MinIO latest, Elasticsearch 9.x). Bumping postgres 16 -> 17 closes the parity | ||
| # gap with the production compose stack so integration tests exercise the same | ||
| # migration / dialect surface the deployed REST + Services see. |
Comment on lines
+21
to
22
| POSTGRES_IMAGE=postgres:17-alpine | ||
| RABBITMQ_IMAGE=rabbitmq:4.1.4-management |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.env.testranpostgres:16-alpinewhile the production compose stack runs Postgres 17 (perCLAUDE.mdstack pins). Bumping the test image closes the parity gap so Testcontainers boot the same major Postgres the deployed REST + Services exercise — same migrations, same dialect, same JSONB / EF Core 10 surface.Closes task #6
The rest of the test infrastructure was already OrbStack-backed:
orbstack(docker context ls→orbstack *)*/Tests/Integration/fixture spins real containers via Testcontainers (Postgres / RabbitMQ / MinIO / Elasticsearch)FakeTextSummarizer— Gemini is third-party and out of scope for local containers (documented inCLAUDE.mdgotchas)Fake*.csfiles are justFakeLoggerExtensionswrappers aroundMicrosoft.Extensions.Diagnostics.Testing.FakeLogger— not a real-deps concernTest plan
./build.sh IntegrationTestslocally —SetupTestcontainers / Restore / Compile / IntegrationTestsall succeeded on bumped imageBuild & Test (backend)green