From 551212e7f9a16d8b3fcbf08a517f8d2f2e28d87f Mon Sep 17 00:00:00 2001 From: Aleksei Sviridkin Date: Tue, 14 Jul 2026 14:59:47 +0300 Subject: [PATCH] fix(docs): refresh trunk version pins to Talos v1.13.6 and Cozystack v1.5.3 The next/ trunk still pinned Talos v1.13.0 while the installer has shipped v1.13.6 for some time, so every install page under next/ told readers to download a Talos release older than the one Cozystack actually installs. The Cozystack pin was equally stale at v1.5.0. Nothing refreshes these pins on its own. update-versions only runs when DOC_VERSION is next, and every release path resolves it to a released version instead: a patch release routes to the existing vX.Y directory, and on a new minor release-next creates that directory before update-all runs. So the release workflow never regenerates the trunk, and the pins drift until someone runs the generator by hand, as here. Regenerated with make update-versions. Assisted-By: Claude Signed-off-by: Aleksei Sviridkin --- data/versions/next.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/data/versions/next.yaml b/data/versions/next.yaml index 48e06b74..167c3598 100644 --- a/data/versions/next.yaml +++ b/data/versions/next.yaml @@ -10,9 +10,9 @@ # RELEASE_TAG when next/ is promoted). # Cozystack release the docs are pinned to. -cozystack_version: "1.5.0" # bare, as used by `helm --version` -cozystack_tag: "v1.5.0" # v-prefixed, as used in GitHub URLs +cozystack_version: "1.5.3" # bare, as used by `helm --version` +cozystack_tag: "v1.5.3" # v-prefixed, as used in GitHub URLs # Talos version shipped by the Cozystack installer for this trunk. -talos: "v1.13.0" +talos: "v1.13.6" talos_minor: "v1.13" # the docs minor used by talos.dev URLs