Skip to content

Commit 551212e

Browse files
committed
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 <[email protected]> Signed-off-by: Aleksei Sviridkin <[email protected]>
1 parent d6f0c10 commit 551212e

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎data/versions/next.yaml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@
1010
# RELEASE_TAG when next/ is promoted).
1111

1212
# Cozystack release the docs are pinned to.
13-
cozystack_version: "1.5.0" # bare, as used by `helm --version`
14-
cozystack_tag: "v1.5.0" # v-prefixed, as used in GitHub URLs
13+
cozystack_version: "1.5.3" # bare, as used by `helm --version`
14+
cozystack_tag: "v1.5.3" # v-prefixed, as used in GitHub URLs
1515

1616
# Talos version shipped by the Cozystack installer for this trunk.
17-
talos: "v1.13.0"
17+
talos: "v1.13.6"
1818
talos_minor: "v1.13" # the docs minor used by talos.dev URLs

0 commit comments

Comments
 (0)