CI - restrict postgres version

[haritamar]

Summary by CodeRabbit

• Chores
  • Updated integration test infrastructure to use a pinned Postgres version, ensuring consistent and reliable test environments.

[linear]

ELE-5147 Fix postgres in OSS CI

[github-actions]

👋 @haritamar
Thank you for raising your pull request.
Please make sure to add tests and document all user-facing changes.
You can do this by editing the docs files in the elementary repository.

[coderabbitai]

Walkthrough

The Postgres service image in the Docker Compose configuration has been updated from an unversioned reference to an explicitly pinned version tag (postgres:15), ensuring consistent deployments across environments.

Changes

Cohort / File(s)	Change Summary
Docker Compose Configuration integration_tests/docker-compose.yml	Updated Postgres service image reference from generic postgres to pinned postgres:15 tag for version consistency

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A postgres pin, so neat and tidy,
Version fifteen, steady Friday,
No more guessing at the tag,
Consistency won't lag! 🏏

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "CI - restrict postgres version" accurately describes the primary change in the pull request, which updates the Postgres service image from a generic "postgres" tag to a pinned "postgres:15" version in the docker-compose.yml file. The title is concise, specific, and clearly communicates that the change restricts the postgres version in the CI configuration. A teammate scanning the git history would immediately understand this change relates to version pinning for the CI environment.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ele-5147-fix-postgres-in-oss-ci

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

integration_tests/docker-compose.yml (1)

5-5: Consider pinning versions for other services as well.

While the Postgres service now has an explicit version tag, ClickHouse (line 16) and pgAdmin (line 33) still use unversioned references (latest and implicitly latest, respectively). This could introduce the same CI flakiness for those services if they release breaking changes. Depending on your stability requirements, consider pinning their versions too—or document why Postgres requires pinning but others don't.

Also applies to: 16-16, 33-33

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between a01c958 and d3f50a4.

📒 Files selected for processing (1)

• integration_tests/docker-compose.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (14)

• GitHub Check: test (fusion, redshift) / test
• GitHub Check: test (latest_official, athena) / test
• GitHub Check: test (fusion, bigquery) / test
• GitHub Check: test (fusion, snowflake) / test
• GitHub Check: test (latest_pre, postgres) / test
• GitHub Check: test (latest_official, databricks_catalog) / test
• GitHub Check: test (latest_official, trino) / test
• GitHub Check: test (latest_official, clickhouse) / test
• GitHub Check: test (latest_official, snowflake) / test
• GitHub Check: test (fusion, databricks_catalog) / test
• GitHub Check: test (latest_official, bigquery) / test
• GitHub Check: test (latest_official, dremio) / test
• GitHub Check: test (latest_official, redshift) / test
• GitHub Check: test (latest_official, postgres) / test

🔇 Additional comments (1)

integration_tests/docker-compose.yml (1)

5-5: Good catch pinning the Postgres version for CI stability.

Pinning to postgres:15 ensures reproducible test runs across environments and prevents unexpected breakage from upstream version changes. This is a best practice for CI infrastructure.