[mortyops]

This PR contains the following updates:

Package	Update	Change
siderolabs/talos	patch	v1.14.4 → v1.14.5

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: (in timezone America/New_York)

• 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 Mend Renovate CLI.

[github-actions]

✅ Automated recommendation: APPROVE

Analysis engine: pr-review-local (openai) · pr-reviewer-action v3.7.0

Recommendation

Approve. This is a clean, single-line patch bump (v1.14.4 → v1.14.5) in talos/machineconfig.yaml.j2. It is a pure digest/tag bump with no other diff noise, and the renovate: datasource annotation is already present.

Change-by-change findings

• talos/machineconfig.yaml.j2 (line 57): image: factory.talos.dev/installer/{{ ENV.SCHEMATIC }}:v1.14.4 → v1.14.5. The # renovate: datasource=docker depName=ghcr.io/siderolabs/installer comment on the preceding line correctly scopes the pin to the ghcr.io/siderolabs/installer datasource (not factory.talos.dev), so the Renovate rule applies. The bump is a patch-level update within the 1.x minor, consistent with the overrides.json5 pin that excludes exactly v1.13.3.

Standards Compliance

• Renovate pin scope: The depName=ghcr.io/siderolabs/installer annotation matches the siderolabs/installer datasource in .renovate/talos.json5. The bump stays within the 1.x minor, so it does not cross the documented pin ceiling.
• No plaintext secrets: The changed line is a public registry image tag — no secret exposure.
• No postRenderer bash: Not applicable to this file.
• No tofu apply follow-on: This is a template change; the standard workflow is just talos upgrade-node (or apply-node for machine-config), not a green-PR auto-apply.
• Naming / layout: talos/machineconfig.yaml.j2 is the canonical Talos template path; no layout violation.

Tool Harness Findings

No tool harness output was included in the corpus.

Unknowns / Needs Verification

• schematic.yaml.j2 drift: The machineconfig.yaml.j2 installer image pin is one of six version pins that can drift from the live cluster. A tuppr TalosUpgrade CR is Flux-applied with rebootMode: powercycle. If the live cluster is already at v1.14.5 (or a newer patch), merging this PR would be a no-op proposal; if it is still at v1.14.4, merging will trigger a node upgrade. The author should confirm the live cluster version before applying — this is a verification item, not a blocker.
• allowedVersions pin in .renovate/overrides.json5: The pin excludes exactly v1.13.3. Since v1.14.5 is well above that ceiling, the bare <X.Y.Z form is not a regression here. No flag needed.

Required Checks

No must_check items were present in the PR classification.

---

Verdict: approve. The change is a single-line, well-annotated patch bump with no side effects on the diff. No blockers or major issues identified.