From 5d3b947bdaabf439b1be212465b249da294f561b Mon Sep 17 00:00:00 2001 From: Giovanni Ferri Date: Tue, 4 Aug 2026 00:18:18 +0100 Subject: [PATCH] pin unraid-lab to Talos v1.14.0-beta.1 for the pipeline proof-of-concept MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit unraid-lab is the sacrificial canary and always takes a prerelease first. oci-lab stays on the global v1.13.7 pin and its files are untouched. Kubernetes is pinned explicitly rather than inherited: the global v1.36.3 belongs to the 1.13 line. v1.37.0-beta.0 is Talos 1.14.0-beta.1's DefaultKubernetesVersion. Merging this does NOT upgrade anything — the unattended runner does not exist yet, and Omni only sees a change when omnictl runs. What it does do is put v1.14.0-beta.1 in the pinned set, so the image the build is about to produce is protected from the pruner. Verified: the resolver returns the override for unraid-lab and v1.13.7 for oci-lab; the renderer emits omni/patches/1.14/ only for the 1.14 target; the drift gate passes. --- omni/versions.yaml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/omni/versions.yaml b/omni/versions.yaml index edd9959..d4c7ccd 100644 --- a/omni/versions.yaml +++ b/omni/versions.yaml @@ -18,7 +18,13 @@ kubernetes: v1.36.3 clusters: # Sacrificial canary. Always takes a prerelease first; recovery is destroy # and re-provision at the previous pin, never a Talos downgrade. - unraid-lab: {} + unraid-lab: + # POC canary for the 1.14 features (openspec: automate-talos-upgrade-pipeline, + # task 8.3). Kubernetes is pinned explicitly because it must not inherit the + # global v1.36.3, which belongs to the 1.13 line. Value is Talos 1.14.0-beta.1's + # DefaultKubernetesVersion. + talos: v1.14.0-beta.1 + kubernetes: v1.37.0-beta.0 # No etcd restore point yet — promotion is gated on a verified backup. oci-lab: {}