[faust-renovate]

This PR contains the following updates:

Package	Update	Change
ghcr.io/joryirving/paseo (source)	digest	f90db21 → 9f347d1

---

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 these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[faust-renovate]

konflate · #1762 — fix(container): update image ghcr.io/joryirving/paseo (f90db21 ➔ 9f347d1)

Tip

Routine: only container-image and chart-version changes; 2 resources across 2 apps

image	from	to	upstream
ghcr.io/joryirving/paseo	0.12.0@sha256:f90db2…	0.12.0@sha256:9f347d…	✅

_{konflate 0.6.6 · rendered 0c8073f}

[faust-review]

Confidence Score: 5/5

[Low risk] The risk remains low because this is a same-version digest replacement for a single application, with the rendered changes confined to its image reference and no indication of central dependency impact or irreversible effects.

Approved

Summary

Moves the paseo image digest while keeping the 0.12.0 tag pinned

The PR replaces one digest of ghcr.io/joryirving/paseo with another under the unchanged 0.12.0 tag, and konflate's render shows that is the whole cluster effect: the pod template of Deployment ai/paseo changes, so the reloader-annotated Deployment recreates the pod when Flux applies it. Because the tag itself does not move, there is no release-note range between the two versions to read: upstream getpaseo/paseo still publishes v0.12.0 as its newest stable release, and the two digests are rebuilds of that same version, so nothing in the changelog applies that was not already in place. The open question the lines raise is why ghcr.io/joryirving/paseo:0.12.0 has been retagged at all: across this PR's revisions Renovate has proposed three different digests (f90db21, a909464, now 9f347d1) for one tag, so the fork's 0.12.0 tag is not immutable upstream and each merge pulls in whatever that rebuild carries, which no notes here describe. Merging is a normal pod restart with no data or config change; the persistence mounts and the projected paseo-config are untouched.

Review context · 1 source · 2/7 commands

• Sources:
  • https://redirect.github.com/getpaseo/paseo/releases
• Commands run: gh konflate

_{Reviews (2) · Last reviewed commit: "fix(container): update image ghcr.io/jor..." · self-qwen3.8-flash-next/low}

[faust-review]

kritika: confidence 5/5 with low risk at a08ed88.

[faust-review]

kritika: confidence 5/5 with low risk at 0c8073f.