chore(deps): update postgres docker tag to v17

[ham-renovate]

This PR contains the following updates:

Package	Update	Change
postgres	major	16-alpine → 17-alpine

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

Summary by CodeRabbit

• Chores
  • Upgraded the database service to version 17, providing performance improvements, security patches, and enhanced stability.

[coderabbitai]

📝 Walkthrough

Walkthrough

The Postgres service image in the docker-compose database configuration was updated from version 16-alpine to version 17-alpine. No changes to services, environment variables, volumes, or health checks.

Changes

Cohort / File(s)	Summary
Database Configuration docker-compose.databases.yml	Updated Postgres service image tag from postgres:16-alpine to postgres:17-alpine.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop hop, a version hop!
From sixteen up to seventeen we go,
Alpine SQL seeds in a row,
Fresher databases in the tech meadow! 🌱

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is missing several required template sections including Issue Number, Type of change, How the change has been tested, and the Change checklist.	Add the missing required sections from the template: Issue Number, Type of change selection, How the change has been tested, and complete the Change checklist.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: updating the PostgreSQL Docker image tag from version 16 to 17.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch renovate/postgres-17.x

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🧹 Nitpick comments (1)

docker-compose.databases.yml (1)

6-6: Developers with an existing postgres_data volume must drop it before pulling this change.

A dump/restore using pg_dumpall, pg_upgrade, or logical replication is required for anyone wishing to migrate data from any previous major release. Concretely, any developer who already has a PG16-initialized postgres_data Docker volume will get a hard FATAL: database files are incompatible with server on the next docker compose up. Since this is a local dev environment (not production), the straightforward fix is:

docker compose -f docker-compose.databases.yml down -v   # drops the old volume
docker compose -f docker-compose.databases.yml up

It would be worth adding a note in CONTRIBUTING.md, the PR description, or wherever onboarding/upgrade notes live so developers aren't caught off guard.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docker-compose.databases.yml` at line 6, Update project docs to warn
developers about the major PostgreSQL upgrade to the new image tag
(postgres:17-alpine) and the incompatible on-disk format: mention that existing
docker volume named postgres_data must be dropped (or data migrated via
pg_dumpall/pg_upgrade/logical replication) before running docker compose -f
docker-compose.databases.yml up, and include the exact shell commands to drop
the volume (docker compose -f docker-compose.databases.yml down -v then up) in
CONTRIBUTING.md and the PR description so contributors aren’t surprised by the
FATAL: database files are incompatible with server error.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@docker-compose.databases.yml`:
- Line 6: Update project docs to warn developers about the major PostgreSQL
upgrade to the new image tag (postgres:17-alpine) and the incompatible on-disk
format: mention that existing docker volume named postgres_data must be dropped
(or data migrated via pg_dumpall/pg_upgrade/logical replication) before running
docker compose -f docker-compose.databases.yml up, and include the exact shell
commands to drop the volume (docker compose -f docker-compose.databases.yml down
-v then up) in CONTRIBUTING.md and the PR description so contributors aren’t
surprised by the FATAL: database files are incompatible with server error.

---

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4318983 and 828ff5e.

📒 Files selected for processing (1)

• docker-compose.databases.yml