chore(deps): update postgres docker tag to v18

[renovate]

This PR contains the following updates:

Package	Update	Change
postgres (source)	major	17 → 18

---

Configuration

📅 Schedule: (UTC)

• 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 was generated by Mend Renovate. View the repository job log.

[anitrend]

OpenCode Dependabot Risk Review

Schema: local-stack.dependabot-risk.v1

Decision: NEUTRAL
Risk: MEDIUM
Automerge allowed: false
Update type: semver-major
Ecosystem: docker

Summary

Renovate proposes upgrading the postgres Docker tag from 17 to 18, a semver-major update to a stateful service. The change is limited to postgres/docker-compose.yaml and no workflow, secret, stack rendering, or deployment files are touched. Because this is a major version bump for a stateful database, the update is classified as neutral per policy and must not be automerged; manual verification of the PostgreSQL 18 upgrade path is required.

Changed runtime artifacts

Image / dependency	From	To	Risk note
postgres	17	18	major version bump of a stateful database service; requires migration (pg_upgrade) and backup verification before rollout

Runtime impact

Major version upgrade of a stateful database service; requires a controlled migration (pg_upgrade or dump/restore), data backup, and validation before the new image is deployed.

Breaking change assessment

Major version upgrade of PostgreSQL (17 to 18); breaking changes and migration steps are expected but release notes were not verified in this analysis.

Required checks

• ./stackctl.sh sync
• ./stackctl.sh up --dry-run --no-logs

Manual follow-up

• Review PostgreSQL 18 release notes and breaking changes
• Verify backup and pg_upgrade migration path for existing data volumes
• Confirm postgres 18 image compatibility with the compose configuration

Sources checked

• Dependabot metadata
• PR diff

[anitrend]

OpenCode risk gate: neutral. Manual review required. Risk: medium. Reason: Renovate proposes upgrading the postgres Docker tag from 17 to 18, a semver-major update to a stateful service. The change is limited to postgres/docker-compose.yaml and no workflow, secret, stack rendering, or deployment files are touched. Because this is a major version bump for a stateful database, the update is classified as neutral per policy and must not be automerged; manual verification of the PostgreSQL 18 upgrade path is required.

[anitrend]

OpenCode risk gate: changes requested. Risk: high. Reason: Renovate proposes upgrading postgres from 17 to 18 (semver major). Postgres is a stateful service and a major version bump requires a controlled data migration (pg_upgrade or dump/restore). The generated stack file stacks/infrastructure.yml is also modified, which is expected given the source compose change, but the migration itself is a manual, high-risk operation that cannot be automated.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.