cozystack preset defaults image to Talos v1.12.6 while the binary carries v1.14 machinery #245

charts/cozystack/values.yaml defaults image to ghcr.io/cozystack/cozystack/talos:v1.12.6, while go.mod has pinned machinery v1.14.0 since the Talos bump. The two have drifted apart.

That was inert until the pre-upgrade path check landed. talm upgrade resolves its target from values.yaml::image, so a cluster already on v1.14.x that hits the chart default is now refused:

refusing this upgrade: host version 1.14.0 is too new to downgrade to Talos 1.12.6

The refusal is correct. Talos supports at most one minor back, and the move really would roll the node back or break its boot; before the guard existed the same invocation sent the RPC and the node found out afterwards. The stale default is the thing to fix.

The preset also pins talosVersion: "v1.12", so the values default and the contract pin agree with each other. What neither tracks is the machinery the binary now carries, which leaves an open question worth answering explicitly: is the cozystack preset deliberately parked at v1.12, or has it simply not been moved?