feat(blog): Cozystack 1.6 release and Blockstor announcement - #641
Conversation
Two posts published through the publishing tools: front matter, page bundles, Open Graph cards and community sections generated rather than hand-assembled, and both validated before the write. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: tym83 <6355522@gmail.com>
|
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. |
|
Warning Review limit reached
Next review available in: 58 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (2)
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 |
IvanHunters
left a comment
IvanHunters
left a comment
There was a problem hiding this comment.
LGTM.
Cross-checked all factual claims against the actual v1.6.0 release notes (gh release view v1.6.0) and repo state — everything matches:
- Release date "July 22, 2026" = actual
publishedAt. - All component versions (Talos 1.13.6, etcd-operator 0.5.2, Cilium 1.19.5, KubeVirt 1.8.4, Velero 1.18.1, VPA 1.5.0, Harbor 2.15.1, Keycloak 26.6.3, LINSTOR 1.33.3 + linstor-csi 1.11.2, FoundationDB 2.30.0, HAMi 2.9.0, Percona Mongo 1.22.0, OpenBao 2.5.1, csi-driver-nfs 4.13.3) match the notes verbatim.
- K8s patches, removal of 1.30, "K8s 1.33+ for management on upgrade from v1.4.x",
maxUnhealthy 50%,sdn.cozystack.ioAPI versions — all confirmed. - Both CVEs (2026-53359, 2026-46113) present in notes; contributor list (incl. first-timer Shreya Baranwal (@shreyaabaranwal)) confirmed.
- v1.5.0 / v1.6.0 tags exist (compare link valid),
cozystack/blockstorrepo public (Apache-2.0), Slack channel + calendar cid identical to the prior 1.5 release post. - Page bundles correct (dir + index.md + banner,
images:front-matter,figureshortcode, valid taxonomies). No draft/TODO/placeholder.
Non-blocking notes:
- The internal Blockstor stats (LOC / test counts / "48 edge cases in v0.1.11" / compat version) live in
cozystack/blockstorand can't be verified from this repo — worth a final cross-check against the Blockstor README before publish. author: "Cozystack Team"is a new convention vs prior personal-author release posts (cosmetic, consistent).
2 participants
Summary
Two posts for the blog:
Both were produced with the publishing tools from #640 rather than assembled by hand, so front matter, the page bundles, the Open Graph cards and the closing community sections are generated and were validated before anything was written.
Verification
Both posts pass the publishing checks with no errors and no warnings, against a full production build. Open Graph cards are 1200×630 PNG, so previews render in Telegram, Slack and LinkedIn.
Rendered pages:
/blog/2026/08/cozystack-1-6-talos-workers-tenant-sso-security-groups-hierarchical-quotas//blog/2026/08/blockstor-linstor-compatible-storage-for-kubernetes/Note on the Blockstor text
The Russian version of this announcement was already published on OpenNet in May. The English text here is not a translation of it: it covers what happened since, including the sixteen releases, the in-place LINSTOR migration tool, the green Cozystack end-to-end run, and an explicit call for contributors.
Unrelated finding, worth a separate issue
While checking the rendered output I noticed the JSON-LD
BlogPostingblock puts the title and description in doubly-quoted form:This is not introduced by these posts — it reproduces on the existing 1.5 and LINSTOR posts too.
layouts/partials/hooks/head-end.htmlappliesjsonifyto values Hugo already returns quoted, so search engines and AI crawlers read a headline wrapped in literal quote characters. Happy to fix it in a separate PR if you agree it should go.