REN-671 / REN-668: the bridge forwards one agent comment per owner message and drops later chat-card run comments (housekeeping). App change reviewed in REN-669 (konairius/matrix-bridge#4, merge f1ad2ea5).
No env, secret, port, registration or network change. State stays in Matrix account data and is read as-is.
Verify
After Flux reconcile: pod 1/1 Ready on /health, 0 restarts, start log line with no errors. No posts in live rooms.
Revert
Revert this commit (image goes back to build.1791062345). Rollout restarts only the matrix-bridge pod; Home Assistant and Synapse are untouched.
## What
Bump `kubernetes/apps/matrix/bridge.yaml` image `matrix-bridge:build.1791062345` → `build.1791152484` (digest `sha256:5e0718f3b28f43ae406e15a14784f085e34b456c3df94f371f0ae2ce907caafa`, = `:f1ad2ea`).
## Why
REN-671 / REN-668: the bridge forwards one agent comment per owner message and drops later chat-card run comments (housekeeping). App change reviewed in REN-669 (konairius/matrix-bridge#4, merge f1ad2ea5).
No env, secret, port, registration or network change. State stays in Matrix account data and is read as-is.
## Verify
After Flux reconcile: pod 1/1 Ready on `/health`, 0 restarts, start log line with no errors. No posts in live rooms.
## Revert
Revert this commit (image goes back to build.1791062345). Rollout restarts only the matrix-bridge pod; Home Assistant and Synapse are untouched.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Approved on 3096ad3d (REN-672). One-line tag bump build.1791062345 -> build.1791152484 in kubernetes/apps/matrix/bridge.yaml; branch is on top of master. Tag = merge f1ad2ea5 of konairius/matrix-bridge#4 (reviewed REN-669, publish green, digest sha256:5e0718f3). Strategy Recreate: a bad pull leaves the bridge down until revert; only matrix-bridge restarts, HA/Synapse untouched. Undo: revert this commit.
Approved on 3096ad3d (REN-672). One-line tag bump build.1791062345 -> build.1791152484 in kubernetes/apps/matrix/bridge.yaml; branch is on top of master. Tag = merge f1ad2ea5 of konairius/matrix-bridge#4 (reviewed REN-669, publish green, digest sha256:5e0718f3). Strategy Recreate: a bad pull leaves the bridge down until revert; only matrix-bridge restarts, HA/Synapse untouched. Undo: revert this commit.
Ghost
merged commit a3e0a3d5c3 into master2026-10-04 22:24:45 +00:00
🤖Automated review — model CLI default (complexity: unknown), commit 3096ad3d80bde5211669747621cd6822fa5bf301.
Advisory review by the review-bot pipeline. It never approves; a human merges. Push new commits to get a fresh review.
Summary
Single-line image tag bump for matrix-bridge in kubernetes/apps/matrix/bridge.yaml (build.1791062345 → build.1791152484), matching the PR description. No env, secret, port, RBAC, or network-policy changes accompany it, and a check of the full manifest confirms that's accurate. No blocking issues.
🟡 Suggestions
kubernetes/apps/matrix/bridge.yaml:124 — the image is referenced by tag only, not pinned by digest, even though the PR body cites a specific digest (sha256:5e0718f3...) for this build. Since build.* tags look immutable-by-convention but aren't enforced as such by the registry, a name@sha256:... reference would make the deployed artifact tamper-proof against a tag re-push. This mirrors the pre-existing style in this file (the old tag wasn't pinned either), so it's not a regression introduced by this PR — just an opportunity if tightening supply-chain guarantees for this workload is a goal.
Tests
No tests apply to this change — it's a plain image reference bump in a Kubernetes manifest. Verification is operational (Flux reconcile + pod health), as described in the PR body's "Verify" section, which is appropriate for this kind of change.
Recommendation
Looks reasonable — no blocking issues; comment above is optional.
🤖 **Automated review** — model `CLI default` (complexity: unknown), commit `3096ad3d80bde5211669747621cd6822fa5bf301`.
> Advisory review by the `review-bot` pipeline. It never approves; a human merges. Push new commits to get a fresh review.
---
## Summary
Single-line image tag bump for `matrix-bridge` in `kubernetes/apps/matrix/bridge.yaml` (`build.1791062345` → `build.1791152484`), matching the PR description. No env, secret, port, RBAC, or network-policy changes accompany it, and a check of the full manifest confirms that's accurate. No blocking issues.
## 🟡 Suggestions
- `kubernetes/apps/matrix/bridge.yaml:124` — the image is referenced by tag only, not pinned by digest, even though the PR body cites a specific digest (`sha256:5e0718f3...`) for this build. Since `build.*` tags look immutable-by-convention but aren't enforced as such by the registry, a `name@sha256:...` reference would make the deployed artifact tamper-proof against a tag re-push. This mirrors the pre-existing style in this file (the old tag wasn't pinned either), so it's not a regression introduced by this PR — just an opportunity if tightening supply-chain guarantees for this workload is a goal.
## Tests
No tests apply to this change — it's a plain image reference bump in a Kubernetes manifest. Verification is operational (Flux reconcile + pod health), as described in the PR body's "Verify" section, which is appropriate for this kind of change.
## Recommendation
Looks reasonable — no blocking issues; comment above is optional.
<!-- pr-review:sha=3096ad3d80bde5211669747621cd6822fa5bf301 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Bump
kubernetes/apps/matrix/bridge.yamlimagematrix-bridge:build.1791062345→build.1791152484(digestsha256:5e0718f3b28f43ae406e15a14784f085e34b456c3df94f371f0ae2ce907caafa, =:f1ad2ea).Why
REN-671 / REN-668: the bridge forwards one agent comment per owner message and drops later chat-card run comments (housekeeping). App change reviewed in REN-669 (konairius/matrix-bridge#4, merge f1ad2ea5).
No env, secret, port, registration or network change. State stays in Matrix account data and is read as-is.
Verify
After Flux reconcile: pod 1/1 Ready on
/health, 0 restarts, start log line with no errors. No posts in live rooms.Revert
Revert this commit (image goes back to build.1791062345). Rollout restarts only the matrix-bridge pod; Home Assistant and Synapse are untouched.
🤖 Generated with Claude Code
Approved on
3096ad3d(REN-672). One-line tag bump build.1791062345 -> build.1791152484 in kubernetes/apps/matrix/bridge.yaml; branch is on top of master. Tag = merge f1ad2ea5 of konairius/matrix-bridge#4 (reviewed REN-669, publish green, digest sha256:5e0718f3). Strategy Recreate: a bad pull leaves the bridge down until revert; only matrix-bridge restarts, HA/Synapse untouched. Undo: revert this commit.🤖 Automated review — model
CLI default(complexity: unknown), commit3096ad3d80bde5211669747621cd6822fa5bf301.Summary
Single-line image tag bump for
matrix-bridgeinkubernetes/apps/matrix/bridge.yaml(build.1791062345→build.1791152484), matching the PR description. No env, secret, port, RBAC, or network-policy changes accompany it, and a check of the full manifest confirms that's accurate. No blocking issues.🟡 Suggestions
kubernetes/apps/matrix/bridge.yaml:124— the image is referenced by tag only, not pinned by digest, even though the PR body cites a specific digest (sha256:5e0718f3...) for this build. Sincebuild.*tags look immutable-by-convention but aren't enforced as such by the registry, aname@sha256:...reference would make the deployed artifact tamper-proof against a tag re-push. This mirrors the pre-existing style in this file (the old tag wasn't pinned either), so it's not a regression introduced by this PR — just an opportunity if tightening supply-chain guarantees for this workload is a goal.Tests
No tests apply to this change — it's a plain image reference bump in a Kubernetes manifest. Verification is operational (Flux reconcile + pod health), as described in the PR body's "Verify" section, which is appropriate for this kind of change.
Recommendation
Looks reasonable — no blocking issues; comment above is optional.