[docs] Update managed apps reference for v1.6.0#628
Merged
Conversation
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
myasnikovdaniil
requested review from
Andrei Kvapil (kvaps) and
Timofei Larkin (lllamnyp)
as code owners
July 22, 2026 16:22
Contributor
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Important Review skippedToo many files! This PR contains 205 files, which is 105 over the limit of 100. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (13)
📒 Files selected for processing (205)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs update for release
v1.6.0— the equivalent of whatupdate-website-docsin cozystack/cozystack'stags.yamlnormally opens. Run by hand because that workflow was never triggered for thev1.6.0tag:v1.6.0is the first stable tag created through the rc→stable promote flow, and the tag push produced no workflow run.Produced by
make release-next RELEASE_TAG=v1.6.0followed bymake update-all BRANCH=release-1.6.0 RELEASE_TAG=v1.6.0, with the commit scoped tocontent/,hugo.yamlanddata/versions/exactly as the workflow stages it.next/is unchanged.One edit beyond the generated output:
data/versions/v1.6.yamlpinstalos: "v1.13.6"instead of thev1.13.0it inherited fromnext.yaml. Cozystack v1.6.0 ships Talos v1.13.6 — bothpackages/core/talos/images/talos/profiles/installer.yamlonrelease-1.6and the v1.6.0 changelog agree — butmake update-allskipsupdate-versionsfor a released version, so the snapshot froze the stale trunk pin. Shipping it unchanged would have pointed v1.6 readers at a Talos release predating the KVM guest-escape CVE fixes that bump was made for.next.yamlitself is deliberately untouched; #618 owns that refresh.