chore(deps): update prom/prometheus docker tag to v3.14.0

[renovate]

This PR contains the following updates:

Package	Update	Change
prom/prometheus	minor	v3.13.2 → v3.14.0

---

Release Notes

prometheus/prometheus (prom/prometheus)

v3.14.0

Compare Source

---

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: UNKNOWN
Automerge allowed: false
Update type: semver-minor
Ecosystem: docker

Summary

Renovate bot proposes a semver-minor update of prom/prometheus from v3.13.2 to v3.14.0. The change touches the source Compose file (observability/prometheus/docker-compose.yml) and the corresponding generated stack (stacks/observability.yml), so the generated stack change has a matching source change. Prometheus is a stateful service requiring extra scrutiny, and the PR's release-notes section is empty, providing no evidence about breaking changes or migration requirements. Because release-note context is missing and no direct blocker was found, the update is returned as neutral rather than approved.

Changed runtime artifacts

Image / dependency	From	To	Risk note
prom/prometheus	v3.13.2	v3.14.0	minor update to a stateful service (prometheus); release notes section is empty so no breaking-change assessment could be made

Runtime impact

Expected rolling service update of the prometheus container; stateful TSDB volume is preserved. Exact runtime impact unverified due to missing release notes.

Breaking change assessment

No release notes were provided in the PR; breaking-change status for v3.14.0 could not be verified.

Required checks

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

Manual follow-up

• Confirm stacks/observability.yml regenerated output matches the source Compose change
• Review prometheus v3.14.0 release notes for any config/flag or storage migration changes before merge

Sources checked

• Renovate PR metadata
• PR diff / changed file list
• Repository source and generated stack files

[anitrend]

OpenCode risk gate: neutral. Manual review required. Risk: unknown. Reason: Renovate bot proposes a semver-minor update of prom/prometheus from v3.13.2 to v3.14.0. The change touches the source Compose file (observability/prometheus/docker-compose.yml) and the corresponding generated stack (stacks/observability.yml), so the generated stack change has a matching source change. Prometheus is a stateful service requiring extra scrutiny, and the PR's release-notes section is empty, providing no evidence about breaking changes or migration requirements. Because release-note context is missing and no direct blocker was found, the update is returned as neutral rather than approved.