fix(docs): refresh trunk version pins to Talos v1.13.6 and Cozystack v1.5.3#618
fix(docs): refresh trunk version pins to Talos v1.13.6 and Cozystack v1.5.3#618Aleksei Sviridkin (lexfrei) wants to merge 1 commit into
Conversation
…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 <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>
Aleksei Sviridkin (lexfrei)
requested review from
Andrei Kvapil (kvaps) and
Timofei Larkin (lllamnyp)
as code owners
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe next release manifest updates Cozystack from 1.5.0 to 1.5.3 and Talos from v1.13.0 to v1.13.6. ChangesNext release version pins
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the Cozystack version to 1.5.3 and the Talos version to v1.13.6 in the data/versions/next.yaml file. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
myasnikovdaniil
left a comment
myasnikovdaniil
left a comment
There was a problem hiding this comment.
Request changes — one correctness issue.
The Talos half is correct and worth landing: talos: v1.13.6 / talos_minor: v1.13 matches the installer profile on cozystack/cozystack@main (packages/core/talos/images/talos/profiles/installer.yaml). But the Cozystack pin is bumped to v1.5.3, which is still a draft release (isDraft: true, publishedAt: null): I verified the exact asset URLs the next/ install docs generate (e.g. .../releases/download/v1.5.3/cozystack-crds.yaml) return 404 on v1.5.3 but 200 on v1.5.2 (the current latest published release). Merging as-is hands readers copy-paste install commands that 404 until v1.5.3 is actually cut. Pin to v1.5.2 (suggestions inline), or hold this PR until v1.5.3 is published.
| # 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` |
There was a problem hiding this comment.
v1.5.3 is a draft release (isDraft:true, publishedAt:null) — helm --version 1.5.3 and the GitHub download URLs built from this pin fail publicly until it's published. Latest final is v1.5.2:
| cozystack_version: "1.5.3" # bare, as used by `helm --version` | |
| cozystack_version: "1.5.2" # bare, as used by `helm --version` |
| 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 |
There was a problem hiding this comment.
Same issue — this tag feeds real download commands in the trunk install docs (install/kubernetes/generic.md, install/talos/iso.md, install/providers/oracle-cloud.md), all of which 404 against the draft:
| cozystack_tag: "v1.5.3" # v-prefixed, as used in GitHub URLs | |
| cozystack_tag: "v1.5.2" # v-prefixed, as used in GitHub URLs |
2 participants
What this PR does
The
next/trunk pinned Talosv1.13.0while the Cozystack installer shipsv1.13.6, so every install page undernext/told readers to download an older Talos than the one Cozystack actually installs. The Cozystack pin was stale too:v1.5.0against a currentv1.5.3.Regenerated
data/versions/next.yamlwithmake update-versions. No hand edits: the file is generated.Why it drifted
Nothing refreshes the trunk pins on its own.
update-versionsonly does work whenDOC_VERSIONisnext, and every release path resolves it to a released version instead:vX.Y/directory;release-nextcreates that directory beforeupdate-allruns.So the release workflow snapshots the trunk into
vX.Y.yamlbut never regenerates the trunk itself. The pins sit still until someone runs the generator by hand, which is what this PR does — they will drift again after the next couple of releases unless the generator is put on a schedule, or the release job refreshesnext/before promoting it.Summary by CodeRabbit