Add missing release announcements for v0.1–v0.41#468
Add missing release announcements for v0.1–v0.41#468tym83 wants to merge 1 commit intocozystack:mainfrom
Conversation
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughAdds 22 new blog post files under Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Add 22 blog posts covering all major releases that were missing from the blog: v0.1, v0.2, v0.3, v0.4, v0.5, v0.6, v0.7, v0.8, v0.9, v0.10, v0.12, v0.13, v0.14, v0.15, v0.19, v0.23, v0.30, v0.37, v0.38, v0.39, v0.40, v0.41. Each post includes key features from the major release and all its patch releases, links to GitHub releases, and community links. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: tym83 <6355522@gmail.com>
tym83
force-pushed
the
blog/add-missing-release-announcements
branch
from
da567d9 to
dde1d71
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 18
🧹 Nitpick comments (3)
content/en/blog/2024-12-04-cozystack-v0-19.md (1)
9-9: Consider removing or shortening the duplicated top heading.Line 9 repeats the full page title from frontmatter; a shorter section heading (or removing this heading) would keep hierarchy cleaner.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-12-04-cozystack-v0-19.md` at line 9, The top-level heading "Cozystack v0.19: Keycloak SSO, Dashboard Services View, KubeVirt v1.4, and MetalLB Update" duplicates the frontmatter title; either remove this duplicated H3 line entirely or replace it with a shorter, subordinate heading (e.g., "Release highlights" or "What's new") to preserve document hierarchy, and update any nearby anchors or internal links that rely on that exact heading text if present.content/en/blog/2024-09-04-cozystack-v0-14.md (1)
9-9: Fix heading level jump at Line 9 (MD001).The first in-body heading starts at
###, which skips##and triggers markdownlint heading-increment. Use##here so subsequent sections nest correctly.Proposed fix
-### Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24 +## Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-09-04-cozystack-v0-14.md` at line 9, The top-level in-body heading "Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24" is using ### and skips a level; change that heading from "### Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24" to use "##" so it becomes "## Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24" to fix the MD001 heading-level-jump and ensure correct nesting of subsequent sections.content/en/blog/2025-12-23-cozystack-v0-39.md (1)
9-9: Optional: Consider using h2 (##) for the first heading to conform to strict Markdown heading hierarchy.The static analysis tool flags that the first heading is h3 instead of h2. While Hugo likely uses the frontmatter
titleas the implicit h1, using h2 (##) for the first content heading would conform to strict Markdown best practices and silence the linter warning.This comment applies to all four blog post files in this PR (v0.38, v0.39, v0.40, v0.41).
📝 Example fix for this file
-### Cozystack v0.39: Topology-Aware Routing, Windows VM Scheduling, Talm Overhaul, and VMAgent for Tenants +## Cozystack v0.39: Topology-Aware Routing, Windows VM Scheduling, Talm Overhaul, and VMAgent for TenantsApply the same change to lines 13, and any other heading levels accordingly (h4 → h3, etc.) if needed for consistency.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2025-12-23-cozystack-v0-39.md` at line 9, The first content heading "Cozystack v0.39: Topology-Aware Routing, Windows VM Scheduling, Talm Overhaul, and VMAgent for Tenants" is an h3 (###) and the linter expects the first content heading to be h2; update that heading from h3 to h2 (and similarly adjust any subsequent heading levels if needed) in this file and apply the same change to the other blog post files for v0.38, v0.40, and v0.41 so the first heading in each content body is ## to satisfy strict Markdown hierarchy.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@content/en/blog/2024-02-20-cozystack-v0-1.md`:
- Line 9: The heading "Cozystack v0.1: ZFS Support, Leader Election, and
Documentation Move" is using ### which skips a level and triggers markdownlint
MD001; change that heading from "### Cozystack v0.1: ZFS Support, Leader
Election, and Documentation Move" to "## Cozystack v0.1: ZFS Support, Leader
Election, and Documentation Move" so the first body heading is H2 and satisfies
the lint rule.
In `@content/en/blog/2024-04-05-cozystack-v0-2.md`:
- Line 9: The heading "### Cozystack v0.2: Bundles, Schema Versioning, FluxCD as
Core Package, and Component Updates" should be demoted one level to "##" to
avoid skipping a heading level (MD001); update that heading token in the
markdown (search for the exact heading text) so the first content heading uses
"##" instead of "###", which will satisfy markdownlint and CI.
In `@content/en/blog/2024-04-18-cozystack-v0-3.md`:
- Line 9: The top-level in-body heading "Cozystack v0.3: Kafka, ClickHouse, and
Hetzner Bare-Metal Support" uses `###` and should be `##` to fix the MD001
heading hierarchy; update that heading from `###` to `##` and leave all
subsequent deeper headings unchanged so the document outline remains valid.
In `@content/en/blog/2024-05-06-cozystack-v0-4.md`:
- Line 9: The top-level content heading currently uses a level-3 heading ("###
Cozystack v0.4: etcd Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix")
which causes a heading level jump; change that heading to level-2 (replace "###"
with "##") so the first content heading starts at "##" and subsequent headings
remain sequential to satisfy markdownlint MD001.
In `@content/en/blog/2024-05-10-cozystack-v0-5.md`:
- Line 9: The first heading after the frontmatter in this post ("Cozystack v0.5:
Automatic Schema Generation, Cilium v1.14.10, and MariaDB Operator Update") is
an h3 (###) but should be h2 (##); update this file and all blog posts that use
an h3 as their first post-heading so the first heading after frontmatter is
`##`. Locate the frontmatter block, find the first markdown heading that follows
it (e.g., the line starting "### Cozystack v0.5...") and change the leading ###
to ##, then run a quick grep or script to apply the same change across all files
in the blog folder to ensure consistent heading hierarchy.
In `@content/en/blog/2024-05-16-cozystack-v0-6.md`:
- Line 9: The heading "Cozystack v0.6: VM Serial Console, Ephemeral Storage for
Containers, and etcd Auto-Quota" uses a level-3 marker (###) and skips a level;
change that marker to level-2 (##) to restore proper heading hierarchy and
satisfy MD001; locate the exact heading text in the blog file
(content/en/blog/2024-05-16-cozystack-v0-6.md) and replace the leading "###"
with "##", ensuring surrounding headings remain sequential.
In `@content/en/blog/2024-05-29-cozystack-v0-7.md`:
- Line 9: The top in-body heading "Cozystack v0.7: Network Stabilization, DNS
Fixes, etcd Autocompaction, and cozy.local Domain" is using "###" which triggers
MD001; change that heading token from "###" to "##" so the first content heading
is level 2 and ensure all existing subsections under it remain one level deeper
(adjust any subsequent headings if needed) to preserve correct heading
hierarchy.
In `@content/en/blog/2024-07-04-cozystack-v0-8.md`:
- Line 9: Change the first in-body heading "### Cozystack v0.8: FluxCD Operator,
E2E Tests, ARM Support, and Managed Cluster Extensions" to use a level-2 heading
(replace the leading "###" with "##") so the top-level in-body heading follows
MD001 rules; update the header text exactly as-is but with "##" to keep heading
increments valid.
In `@content/en/blog/2024-07-10-cozystack-v0-9.md`:
- Line 9: Change the post body heading "Cozystack v0.9: KubeVirt v1.2.2, Kamaji
v1.0, Tenant K8s v1.30, and Node Group Upgrades" from a level-3 header (###) to
a level-2 header (##) so heading levels increment correctly at the start of the
post; locate that exact heading text in
content/en/blog/2024-07-10-cozystack-v0-9.md and replace the leading "###" with
"##".
In `@content/en/blog/2024-07-23-cozystack-v0-10.md`:
- Line 9: The top-level content heading currently uses "### Cozystack v0.10:
FerretDB, NATS, Network Policies for Tenant Isolation, and etcd Operator v0.4"
which triggers MD001; update that heading token from "###" to "##" so the first
content heading is an H2 (change the heading for the exact string "Cozystack
v0.10: FerretDB, NATS, Network Policies for Tenant Isolation, and etcd Operator
v0.4").
In `@content/en/blog/2024-08-21-cozystack-v0-12.md`:
- Line 9: The first body heading in
content/en/blog/2024-08-21-cozystack-v0-12.md uses a level-3 heading ("###
Cozystack v0.12: ...") which skips the top-level document heading and triggers
markdownlint MD001; change that heading to a level-2 heading ("## Cozystack
v0.12: StorageClass for All Apps, Cilium v1.16, VM Configuration, and E2E
Sandbox") so the first section title follows the document title hierarchy
(update the "### Cozystack v0.12: StorageClass for All Apps, Cilium v1.16, VM
Configuration, and E2E Sandbox" line to use "##").
In `@content/en/blog/2024-08-31-cozystack-v0-13.md`:
- Line 9: The first in-content heading "Cozystack v0.13: VictoriaLogs, VM Live
Migration, KubeVirt v1.3, and Bridge Networking" is currently a level-3 heading
(###) which triggers MD001; change that line to a level-2 heading (##) so the
document starts with an H2 for the first in-content heading and resolves the
MD001 lint warning.
In `@content/en/blog/2024-09-16-cozystack-v0-15.md`:
- Line 9: The heading "Cozystack v0.15: OpenCost, Talos Metal Image, Backup
Fixes, and Kamaji OOM Fix" is using ### which jumps a level and triggers MD001;
change that heading token from ### to ## so the first body heading uses a
second-level header and fixes the markdownlint error (locate the line containing
that exact heading text and update the leading hashes).
In `@content/en/blog/2025-01-17-cozystack-v0-23.md`:
- Line 9: The document heading "Cozystack v0.23: Talos Linux v1.9.2, Telegram
Alert Severity, VM Instance Hooks, and Flux Operator Update" is using h3 (###)
but should be h2 (##) as the first heading after frontmatter; update that
heading marker from ### to ## so the file's top-level structure and
accessibility are correct, ensuring the line that currently reads "### Cozystack
v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM Instance Hooks, and Flux
Operator Update" is changed to "## Cozystack v0.23: Talos Linux v1.9.2, Telegram
Alert Severity, VM Instance Hooks, and Flux Operator Update".
- Line 37: The "All changes" line references GitHub release tags v0.23.0 and
v0.23.1 that don't appear to exist; update the two release links (the literal
strings "v0.23.0" and "v0.23.1" in the All changes line) to point to the correct
existing release tags (for example v0.40.0, v0.41.0, or v1.0.0) or remove them
if there is no matching release, ensuring the displayed link text matches the
actual GitHub release tag URL.
- Around line 15-35: The post references non-existent release tags v0.23.0 and
v0.23.1 (see the "v0.23.1: Fixed dashboard error" line and any release links),
so update the release references to actual tags or remove them: either replace
"v0.23.1" and any v0.23.x links with the correct existing release (e.g., v0.41.x
or the appropriate current tag) and adjust the Fixes bullet to match the real
release notes, or delete the incorrect release line and broken links entirely;
ensure any linked GitHub release URLs match the new tag strings.
In `@content/en/blog/2025-04-10-cozystack-v0-30.md`:
- Line 9: The heading "Cozystack v0.30: GPU Passthrough, WorkloadMonitor for
PVCs and IPs, CPUManager, and Automated Testing in CI" is currently an h3 (###);
change it to h2 (##) so the Markdown hierarchy increments correctly from the
top-level title to this section—locate the line containing that exact heading
text and replace the leading "###" with "##" to fix the document structure.
In `@content/en/blog/2025-10-10-cozystack-v0-37.md`:
- Line 4: The front-matter date for the blog post is incorrect: update the date
field in the file (the "date:" entry in
content/en/blog/2025-10-10-cozystack-v0-37.md) to the actual v0.37.0 release
date (e.g. change "2025-10-10" to "2025-11-04" or the verified November 2025
release date) so the post timestamp matches the release.
---
Nitpick comments:
In `@content/en/blog/2024-09-04-cozystack-v0-14.md`:
- Line 9: The top-level in-body heading "Cozystack v0.14: Auto-Generated
Passwords, RabbitMQ Users and VHosts, and CNPG v1.24" is using ### and skips a
level; change that heading from "### Cozystack v0.14: Auto-Generated Passwords,
RabbitMQ Users and VHosts, and CNPG v1.24" to use "##" so it becomes "##
Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG
v1.24" to fix the MD001 heading-level-jump and ensure correct nesting of
subsequent sections.
In `@content/en/blog/2024-12-04-cozystack-v0-19.md`:
- Line 9: The top-level heading "Cozystack v0.19: Keycloak SSO, Dashboard
Services View, KubeVirt v1.4, and MetalLB Update" duplicates the frontmatter
title; either remove this duplicated H3 line entirely or replace it with a
shorter, subordinate heading (e.g., "Release highlights" or "What's new") to
preserve document hierarchy, and update any nearby anchors or internal links
that rely on that exact heading text if present.
In `@content/en/blog/2025-12-23-cozystack-v0-39.md`:
- Line 9: The first content heading "Cozystack v0.39: Topology-Aware Routing,
Windows VM Scheduling, Talm Overhaul, and VMAgent for Tenants" is an h3 (###)
and the linter expects the first content heading to be h2; update that heading
from h3 to h2 (and similarly adjust any subsequent heading levels if needed) in
this file and apply the same change to the other blog post files for v0.38,
v0.40, and v0.41 so the first heading in each content body is ## to satisfy
strict Markdown hierarchy.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 8c4e84fa-553c-4c85-8f62-9e2995e4aae2
📒 Files selected for processing (22)
content/en/blog/2024-02-20-cozystack-v0-1.mdcontent/en/blog/2024-04-05-cozystack-v0-2.mdcontent/en/blog/2024-04-18-cozystack-v0-3.mdcontent/en/blog/2024-05-06-cozystack-v0-4.mdcontent/en/blog/2024-05-10-cozystack-v0-5.mdcontent/en/blog/2024-05-16-cozystack-v0-6.mdcontent/en/blog/2024-05-29-cozystack-v0-7.mdcontent/en/blog/2024-07-04-cozystack-v0-8.mdcontent/en/blog/2024-07-10-cozystack-v0-9.mdcontent/en/blog/2024-07-23-cozystack-v0-10.mdcontent/en/blog/2024-08-21-cozystack-v0-12.mdcontent/en/blog/2024-08-31-cozystack-v0-13.mdcontent/en/blog/2024-09-04-cozystack-v0-14.mdcontent/en/blog/2024-09-16-cozystack-v0-15.mdcontent/en/blog/2024-12-04-cozystack-v0-19.mdcontent/en/blog/2025-01-17-cozystack-v0-23.mdcontent/en/blog/2025-04-10-cozystack-v0-30.mdcontent/en/blog/2025-10-10-cozystack-v0-37.mdcontent/en/blog/2025-11-25-cozystack-v0-38.mdcontent/en/blog/2025-12-23-cozystack-v0-39.mdcontent/en/blog/2026-01-10-cozystack-v0-40.mdcontent/en/blog/2026-01-20-cozystack-v0-41.md
| description: "The first feature release of Cozystack introduces ZFS storage support, leader election for the controller, and moves documentation to cozystack.io." | ||
| --- | ||
|
|
||
| ### Cozystack v0.1: ZFS Support, Leader Election, and Documentation Move |
There was a problem hiding this comment.
Fix heading-level jump at Line 9 to satisfy markdownlint MD001.
The first body heading starts at ###, which skips a level and can fail lint/docs checks. Use ## here.
Proposed fix
-### Cozystack v0.1: ZFS Support, Leader Election, and Documentation Move
+## Cozystack v0.1: ZFS Support, Leader Election, and Documentation Move📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.1: ZFS Support, Leader Election, and Documentation Move | |
| ## Cozystack v0.1: ZFS Support, Leader Election, and Documentation Move |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2024-02-20-cozystack-v0-1.md` at line 9, The heading
"Cozystack v0.1: ZFS Support, Leader Election, and Documentation Move" is using
### which skips a level and triggers markdownlint MD001; change that heading
from "### Cozystack v0.1: ZFS Support, Leader Election, and Documentation Move"
to "## Cozystack v0.1: ZFS Support, Leader Election, and Documentation Move" so
the first body heading is H2 and satisfies the lint rule.
| description: "Cozystack v0.2 introduces bundle-based installation, schema versioning for charts, moves FluxCD to the core, and updates Cilium, LINSTOR, CNPG, and MariaDB Operator." | ||
| --- | ||
|
|
||
| ### Cozystack v0.2: Bundles, Schema Versioning, FluxCD as Core Package, and Component Updates |
There was a problem hiding this comment.
Adjust heading level at Line 9 (### → ##) to avoid MD001 warning.
Current heading depth skips a level for the first content heading and may break markdownlint in CI.
Proposed fix
-### Cozystack v0.2: Bundles, Schema Versioning, FluxCD as Core Package, and Component Updates
+## Cozystack v0.2: Bundles, Schema Versioning, FluxCD as Core Package, and Component Updates📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.2: Bundles, Schema Versioning, FluxCD as Core Package, and Component Updates | |
| ## Cozystack v0.2: Bundles, Schema Versioning, FluxCD as Core Package, and Component Updates |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2024-04-05-cozystack-v0-2.md` at line 9, The heading "###
Cozystack v0.2: Bundles, Schema Versioning, FluxCD as Core Package, and
Component Updates" should be demoted one level to "##" to avoid skipping a
heading level (MD001); update that heading token in the markdown (search for the
exact heading text) so the first content heading uses "##" instead of "###",
which will satisfy markdownlint and CI.
| description: "Cozystack v0.3 adds Kafka and ClickHouse as managed applications and introduces NoCloud assets for Hetzner bare-metal installation." | ||
| --- | ||
|
|
||
| ### Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal Support |
There was a problem hiding this comment.
Use ## for the first in-body heading to fix heading hierarchy.
Line 9 starts at ###, which skips a level and triggers MD001. Change it to ## (and keep deeper sections relative to it) to preserve a valid outline.
Suggested diff
-### Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal Support
+## Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal Support📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal Support | |
| ## Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal Support |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2024-04-18-cozystack-v0-3.md` at line 9, The top-level
in-body heading "Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal
Support" uses `###` and should be `##` to fix the MD001 heading hierarchy;
update that heading from `###` to `##` and leave all subsequent deeper headings
unchanged so the document outline remains valid.
| description: "Cozystack v0.4 replaces kamaji-etcd with the new aenix-io/etcd-operator, adds replica configuration for applications, and updates Kamaji, LINSTOR, and Kubeapps." | ||
| --- | ||
|
|
||
| ### Cozystack v0.4: etcd Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix |
There was a problem hiding this comment.
Fix heading level jump at Line 9 (### → ##).
This triggers markdownlint MD001 (heading increment). Start the first content heading at ## so subsequent levels remain sequential.
Suggested fix
-### Cozystack v0.4: etcd Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix
+## Cozystack v0.4: etcd Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.4: etcd Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix | |
| ## Cozystack v0.4: etcd Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2024-05-06-cozystack-v0-4.md` at line 9, The top-level
content heading currently uses a level-3 heading ("### Cozystack v0.4: etcd
Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix") which causes a
heading level jump; change that heading to level-2 (replace "###" with "##") so
the first content heading starts at "##" and subsequent headings remain
sequential to satisfy markdownlint MD001.
| description: "Cozystack v0.5 adds automatic Helm schema generation, removes hardcoded defaults, and updates Cilium and MariaDB Operator." | ||
| --- | ||
|
|
||
| ### Cozystack v0.5: Automatic Schema Generation, Cilium v1.14.10, and MariaDB Operator Update |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check heading levels in all new blog post files to identify if the h3 pattern is consistent.
# Find all new blog post files and check their first heading level
fd -e md . content/en/blog/ --exec sh -c 'echo "=== {} ===" && head -20 {} | grep -E "^#{1,6} " | head -1'Repository: cozystack/website
Length of output: 10246
Fix heading hierarchy across all blog posts.
The first heading after frontmatter should be h2 (##), not h3 (###). This issue is consistent across nearly all blog posts (50+ files checked), violating markdown heading hierarchy standards and affecting document structure and accessibility.
📝 Proposed fix
-### Cozystack v0.5: Automatic Schema Generation, Cilium v1.14.10, and MariaDB Operator Update
+## Cozystack v0.5: Automatic Schema Generation, Cilium v1.14.10, and MariaDB Operator UpdateApply the same correction across all blog post files in content/en/blog/ that use h3 as the first heading.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.5: Automatic Schema Generation, Cilium v1.14.10, and MariaDB Operator Update | |
| ## Cozystack v0.5: Automatic Schema Generation, Cilium v1.14.10, and MariaDB Operator Update |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2024-05-10-cozystack-v0-5.md` at line 9, The first heading
after the frontmatter in this post ("Cozystack v0.5: Automatic Schema
Generation, Cilium v1.14.10, and MariaDB Operator Update") is an h3 (###) but
should be h2 (##); update this file and all blog posts that use an h3 as their
first post-heading so the first heading after frontmatter is `##`. Locate the
frontmatter block, find the first markdown heading that follows it (e.g., the
line starting "### Cozystack v0.5...") and change the leading ### to ##, then
run a quick grep or script to apply the same change across all files in the blog
folder to ensure consistent heading hierarchy.
| description: "Cozystack v0.23 updates Talos Linux to v1.9.2, adds Telegram severity filtering for alerts, introduces hooks for VM instance type updates, and updates the FluxCD Operator." | ||
| --- | ||
|
|
||
| ### Cozystack v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM Instance Hooks, and Flux Operator Update |
There was a problem hiding this comment.
Fix the heading hierarchy.
The first heading after frontmatter should use h2 (##) instead of h3 (###) to maintain proper document structure and accessibility.
📝 Proposed fix for heading level
-### Cozystack v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM Instance Hooks, and Flux Operator Update
+## Cozystack v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM Instance Hooks, and Flux Operator Update📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM Instance Hooks, and Flux Operator Update | |
| ## Cozystack v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM Instance Hooks, and Flux Operator Update |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2025-01-17-cozystack-v0-23.md` at line 9, The document
heading "Cozystack v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM
Instance Hooks, and Flux Operator Update" is using h3 (###) but should be h2
(##) as the first heading after frontmatter; update that heading marker from ###
to ## so the file's top-level structure and accessibility are correct, ensuring
the line that currently reads "### Cozystack v0.23: Talos Linux v1.9.2, Telegram
Alert Severity, VM Instance Hooks, and Flux Operator Update" is changed to "##
Cozystack v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM Instance Hooks,
and Flux Operator Update".
| #### Talos Linux v1.9.2 | ||
|
|
||
| Talos Linux is updated to **v1.9.2**, bringing security patches and stability improvements for the host OS. | ||
|
|
||
| #### Telegram Alert Severity Filtering | ||
|
|
||
| Operators can now configure **severity filtering** for Telegram alert notifications, reducing noise by only forwarding alerts of a specified severity level or higher. | ||
|
|
||
| #### VM Instance Hooks | ||
|
|
||
| New hooks enable updating **instanceType**, **instanceProfile**, and **storage** on virtual machines, making VM lifecycle management more flexible and scriptable. | ||
|
|
||
| #### FluxCD Operator v0.13.0 | ||
|
|
||
| The FluxCD Operator is updated to **v0.13.0** with improved reconciliation. | ||
|
|
||
| #### Fixes | ||
|
|
||
| - Fixed monitoring nil checker for edge cases. | ||
| - Fixed Keycloak configure reconciliation. | ||
| - v0.23.1: Fixed dashboard error "Unable to get installed package". |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Fetch GitHub release notes for v0.23.0 and v0.23.1 to verify accuracy
echo "=== Fetching v0.23.0 release notes ==="
gh release view v0.23.0 --repo cozystack/cozystack --json body,tagName,publishedAt | jq -r '.body'
echo -e "\n=== Fetching v0.23.1 release notes ==="
gh release view v0.23.1 --repo cozystack/cozystack --json body,tagName,publishedAt | jq -r '.body'Repository: cozystack/website
Length of output: 434
🌐 Web query:
Cozystack v0.23.0 release notes
💡 Result:
No release notes for Cozystack v0.23.0 were found. The official GitHub releases page (https://github.com/cozystack/cozystack/releases) lists v0 releases up to v0.40.0 and higher v1.x versions, but no v0.23.0. Documentation mentions v0.x series exists with a v0 to v1 upgrade path, but specific v0.23.0 does not appear in search results across multiple queries targeting releases, changelogs, and GitHub. It may be an outdated, unindexed, or non-existent version tag. Check the full releases list directly or earlier tags on GitHub for confirmation.
Citations:
- 1: https://github.com/cozystack/cozystack/releases
- 2: https://cozystack.io/docs/
- 3: https://github.com/cozystack/cozystack/releases/tag/v1.0.0
- 4: https://github.com/cozystack/cozystack
- 5: https://github.com/cozystack/cozystack/releases/tag/v0.40.0
🏁 Script executed:
#!/bin/bash
# Search for CHANGELOG or release documentation in the repository
find . -type f \( -name "CHANGELOG*" -o -name "RELEASES*" -o -name "release*" \) | head -20Repository: cozystack/website
Length of output: 43
🏁 Script executed:
#!/bin/bash
# Search for version references in the repository to understand release structure
rg "v0\.23\.(0|1)" --type markdown | head -30Repository: cozystack/website
Length of output: 376
🌐 Web query:
Cozystack GitHub releases v0.23 v0.40 complete list
💡 Result:
The complete list of Cozystack GitHub releases from v0.23 to v0.40 is not explicitly enumerated in search results, as the releases page shows recent releases (v1.x and late v0.4x) but not older v0.2x pages directly. v0.40.0 exists (released 2026-01-10), but no specific v0.23.0 page was found, suggesting v0.23 may not exist or is too old. The full list is available at https://github.com/cozystack/cozystack/releases, with 185 total releases per repo page. Recent v0.x: v0.41.0 (2026-01-20), v0.40.0. v1.0.0 marks major architecture change from v0.x.
Citations:
- 1: https://github.com/cozystack/cozystack/releases
- 2: https://github.com/cozystack/cozystack/releases/tag/v0.40.0
- 3: https://github.com/cozystack/cozystack
- 4: https://github.com/cozystack/cozystack/releases/tag/v1.0.0
- 5: https://github.com/cozystack/cozystack/releases/tag/v0.41.0
🏁 Script executed:
#!/bin/bash
# Try to fetch the actual releases using curl with GitHub API without authentication
# This attempts to list releases for cozystack/cozystack repository
curl -s "https://api.github.com/repos/cozystack/cozystack/releases?per_page=100" | jq -r '.[] | .tag_name' | head -50Repository: cozystack/website
Length of output: 504
🏁 Script executed:
#!/bin/bash
# Fetch all releases to check if v0.23 exists anywhere
curl -s "https://api.github.com/repos/cozystack/cozystack/releases?per_page=200" | jq -r '.[] | .tag_name' | grep -E "v0\.23"Repository: cozystack/website
Length of output: 43
🏁 Script executed:
#!/bin/bash
# Also check for any v0.2x versions
curl -s "https://api.github.com/repos/cozystack/cozystack/releases?per_page=200" | jq -r '.[] | .tag_name' | grep -E "v0\.2[0-9]"Repository: cozystack/website
Length of output: 43
🏁 Script executed:
#!/bin/bash
# Check if there's any documentation in the repo about what version this blog post should actually be for
cat content/en/blog/2025-01-17-cozystack-v0-23.md | head -20Repository: cozystack/website
Length of output: 857
Remove or correct broken release references: v0.23.0 and v0.23.1 do not exist in the Cozystack GitHub repository.
The blog post links to releases (https://github.com/cozystack/cozystack/releases/tag/v0.23.0 and v0.23.1) that do not exist. A search of the official cozystack/cozystack repository confirms that the latest v0.x releases are v0.41.x—there is no v0.23.x series. Either the version numbers are incorrect, or this blog post should reference an actual existing release (e.g., v0.41.x or later).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2025-01-17-cozystack-v0-23.md` around lines 15 - 35, The post
references non-existent release tags v0.23.0 and v0.23.1 (see the "v0.23.1:
Fixed dashboard error" line and any release links), so update the release
references to actual tags or remove them: either replace "v0.23.1" and any
v0.23.x links with the correct existing release (e.g., v0.41.x or the
appropriate current tag) and adjust the Fixes bullet to match the real release
notes, or delete the incorrect release line and broken links entirely; ensure
any linked GitHub release URLs match the new tag strings.
| - Fixed Keycloak configure reconciliation. | ||
| - v0.23.1: Fixed dashboard error "Unable to get installed package". | ||
|
|
||
| All changes: [v0.23.0](https://github.com/cozystack/cozystack/releases/tag/v0.23.0), [v0.23.1](https://github.com/cozystack/cozystack/releases/tag/v0.23.1) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify that the GitHub release tags exist and are accessible
echo "=== Checking v0.23.0 release ==="
gh release view v0.23.0 --repo cozystack/cozystack --json url,tagName,publishedAt
echo -e "\n=== Checking v0.23.1 release ==="
gh release view v0.23.1 --repo cozystack/cozystack --json url,tagName,publishedAtRepository: cozystack/website
Length of output: 422
🌐 Web query:
CozyStack v0.23.0 v0.23.1 GitHub releases
💡 Result:
No GitHub releases for CozyStack (cozystack/cozystack) v0.23.0 or v0.23.1 were found. The project has 185 releases, with recent v0.x versions including v0.40.0 (2026-01-10) and v0.41.0 (2026-01-20), followed by v1.0.0 (2026-02-26). These specific versions do not appear in release pages, changelogs, or search results. Note that cozy/cozy-stack (a different project) exists but uses different versioning (e.g., 1.6.x).
Citations:
- 1: https://github.com/cozystack/cozystack/releases
- 2: https://github.com/cozystack/cozystack/releases/tag/v1.0.0
- 3: https://github.com/cozy/cozy-stack/releases
- 4: https://github.com/cozystack/cozystack
- 5: https://github.com/cozystack/cozystack/releases/tag/v0.41.0
- 6: https://github.com/cozystack/cozystack/releases/tag/v0.40.0
- 7: https://newreleases.io/project/github/cozystack/cozystack/release/v0.40.0
🌐 Web query:
cozystack/cozystack releases v0.23.0 v0.23.1
💡 Result:
Cozystack/cozystack releases v0.23.0 and v0.23.1 were early versions released shortly after v0.22.0. A LinkedIn post from Ænix (the original sponsor) announced them together, noting updates including Talos Linux to v1.9.2. These predate the v1.0.0 major release in February 2026, which evolved the architecture from v0.x. Detailed changelogs are available on the GitHub releases page, but specific v0.23.x pages were not surfaced in searches; higher v0.x like v0.40.0 and v0.41.0 show continued development with features like enhanced storage and MongoDB support. The project has 185 releases total, latest v1.2.1 as of March 2026. v0 docs are archived at https://cozystack.io/docs/v0/.
Citations:
- 1: https://github.com/cozystack/cozystack/releases
- 2: https://www.linkedin.com/posts/aenix-io_release-v0231-aenix-iocozystack-activity-7286425865037512705-QyXs
- 3: https://github.com/aenix-io/cozystack
- 4: https://github.com/aenix-io/cozystack/releases/tag/v0.19.0
- 5: https://blog.aenix.io/cozystack-v0-20-release-terraform-keycloak-and-stability-security-improvements-55dd25335e6e
The v0.23.0 and v0.23.1 release links may not exist on GitHub.
GitHub searches for cozystack/cozystack do not return v0.23.0 or v0.23.1 releases. The project has 185 releases total, with recent v0.x versions including v0.40.0 and v0.41.0, followed by v1.0.0. Verify that these release tags are correct or update the links to point to the actual release versions.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2025-01-17-cozystack-v0-23.md` at line 37, The "All changes"
line references GitHub release tags v0.23.0 and v0.23.1 that don't appear to
exist; update the two release links (the literal strings "v0.23.0" and "v0.23.1"
in the All changes line) to point to the correct existing release tags (for
example v0.40.0, v0.41.0, or v1.0.0) or remove them if there is no matching
release, ensuring the displayed link text matches the actual GitHub release tag
URL.
| description: "Cozystack v0.30 introduces GPU support for virtual machines, WorkloadMonitor tracking for PVCs and public IPs, CPUManager for dedicated CPU instances, and automated release testing." | ||
| --- | ||
|
|
||
| ### Cozystack v0.30: GPU Passthrough, WorkloadMonitor for PVCs and IPs, CPUManager, and Automated Testing in CI |
There was a problem hiding this comment.
Fix the heading level to follow Markdown hierarchy.
The heading should use ## (h2) instead of ### (h3) to maintain proper document structure. Markdown headings should increment by one level at a time (h1 → h2 → h3), not skip levels.
📝 Proposed fix for heading structure
-### Cozystack v0.30: GPU Passthrough, WorkloadMonitor for PVCs and IPs, CPUManager, and Automated Testing in CI
+## Cozystack v0.30: GPU Passthrough, WorkloadMonitor for PVCs and IPs, CPUManager, and Automated Testing in CI📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.30: GPU Passthrough, WorkloadMonitor for PVCs and IPs, CPUManager, and Automated Testing in CI | |
| ## Cozystack v0.30: GPU Passthrough, WorkloadMonitor for PVCs and IPs, CPUManager, and Automated Testing in CI |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2025-04-10-cozystack-v0-30.md` at line 9, The heading
"Cozystack v0.30: GPU Passthrough, WorkloadMonitor for PVCs and IPs, CPUManager,
and Automated Testing in CI" is currently an h3 (###); change it to h2 (##) so
the Markdown hierarchy increments correctly from the top-level title to this
section—locate the line containing that exact heading text and replace the
leading "###" with "##" to fix the document structure.
| --- | ||
| title: "Cozystack v0.37: OpenAPI Dashboard, Lineage Webhook, PVC Expansion in Tenants, and SeaweedFS S3 Discovery" | ||
| slug: cozystack-v0-37 | ||
| date: 2025-10-10 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify that the blog post date matches the v0.37.0 GitHub release date
# Fetch the v0.37.0 release date from GitHub
gh api repos/cozystack/cozystack/releases/tags/v0.37.0 --jq '.published_at' | head -c 10
echo ""
echo "Expected date in frontmatter: (result above in YYYY-MM-DD format)"
echo "Actual date in frontmatter: 2025-10-10"Repository: cozystack/website
Length of output: 224
🌐 Web query:
cozystack v0.37.0 release date October 2025
💡 Result:
Cozystack v0.37.0 was released in early November 2025, prior to November 4, 2025. A blog post published on November 4, 2025, refers to it as "the new release" featuring a brand new UI, indicating recent release. v0.37.1 followed shortly after. The official GitHub releases page lists later versions starting from v0.38.x in late November 2025, but v0.37.0 exists as evidenced by references in changelogs and docs. It was not released in October 2025.
Citations:
- 1: https://blog.aenix.io/cozystack-v0-37-brand-new-ui-dd4ad96eac57
- 2: https://newreleases.io/project/github/cozystack/cozystack/release/v0.37.1
- 3: https://github.com/cozystack/cozystack/releases
- 4: https://github.com/cozystack/cozystack/releases/tag/v0.38.1
🏁 Script executed:
#!/bin/bash
# Try to fetch the release without authentication using curl
curl -s "https://api.github.com/repos/cozystack/cozystack/releases/tags/v0.37.0" | grep -o '"published_at":"[^"]*"' | head -1Repository: cozystack/website
Length of output: 43
Correct the publication date to match the actual v0.37.0 release date.
The date field is set to 2025-10-10, but v0.37.0 was released in early November 2025 (prior to November 4, 2025). Update the date to align with the actual release date, likely 2025-11-04 or earlier in November to maintain accurate chronology.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2025-10-10-cozystack-v0-37.md` at line 4, The front-matter
date for the blog post is incorrect: update the date field in the file (the
"date:" entry in content/en/blog/2025-10-10-cozystack-v0-37.md) to the actual
v0.37.0 release date (e.g. change "2025-10-10" to "2025-11-04" or the verified
November 2025 release date) so the post timestamp matches the release.
![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 introduces a series of blog posts documenting the release history of Cozystack from version 0.1 to 0.41. The review feedback identifies several critical issues regarding factual accuracy, specifically hallucinated component versions and incorrect publication dates that conflict with the official release history. Additionally, there are suggestions to improve maintainability by using Hugo shortcodes for repetitive community links, removing redundant headers, and correcting typos in component names.
|
|
||
| #### Component Updates | ||
|
|
||
| - Piraeus Operator and LINSTOR v2.4.1 |
There was a problem hiding this comment.
The version numbers in this post (e.g., LINSTOR v2.4.1) do not match the actual v0.2.0 release history. It appears the AI generator has hallucinated future version numbers. Please cross-reference all feature descriptions and component versions with the official GitHub release notes.
| - Piraeus Operator and LINSTOR v2.4.1 | |
| - Piraeus Operator v2.2.0 and LINSTOR v1.26.2 |
| --- | ||
| title: "Cozystack v0.19: Keycloak SSO, Dashboard Services View, KubeVirt v1.4, and MetalLB Update" | ||
| slug: cozystack-v0-19 | ||
| date: 2024-12-04 |
There was a problem hiding this comment.
The publication date (2024-12-04) is incorrect. Cozystack v0.19 was released in May 2024. This systematic error in dates (shifting them forward) affects most posts in this PR. Please verify all dates against the GitHub release history to ensure the blog timeline is accurate.
| date: 2024-12-04 | |
| date: 2024-05-24 |
| ### Cozystack v0.1: ZFS Support, Leader Election, and Documentation Move | ||
|
|
There was a problem hiding this comment.
The H3 title is redundant as it repeats the frontmatter title, which is typically rendered by the Hugo template. Consider removing it to avoid double titles in the blog post.
| ### Join the community | ||
|
|
||
| - Telegram [group](https://t.me/cozystack) | ||
| - Slack [group](https://kubernetes.slack.com/archives/C06L3CPRVN1) (Get invite at [https://slack.kubernetes.io](https://slack.kubernetes.io)) | ||
| - [Community Meeting Calendar](https://calendar.google.com/calendar?cid=ZTQzZDIxZTVjOWI0NWE5NWYyOGM1ZDY0OWMyY2IxZTFmNDMzZTJlNjUzYjU2ZGJiZGE3NGNhMzA2ZjBkMGY2OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t) | ||
| - [YouTube](https://www.youtube.com/@cozystack) |
There was a problem hiding this comment.
The 'Join the community' section is duplicated across all 22 new blog posts. To improve maintainability and ensure consistency, consider moving this block into a Hugo shortcode (e.g., {{< community-links >}}).
| ### Join the community | |
| - Telegram [group](https://t.me/cozystack) | |
| - Slack [group](https://kubernetes.slack.com/archives/C06L3CPRVN1) (Get invite at [https://slack.kubernetes.io](https://slack.kubernetes.io)) | |
| - [Community Meeting Calendar](https://calendar.google.com/calendar?cid=ZTQzZDIxZTVjOWI0NWE5NWYyOGM1ZDY0OWMyY2IxZTFmNDMzZTJlNjUzYjU2ZGJiZGE3NGNhMzA2ZjBkMGY2OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t) | |
| - [YouTube](https://www.youtube.com/@cozystack) | |
| {{< community-links >}} |
| - Cilium v1.18.5 | ||
| - Kube-OVN v1.14.25 | ||
| - Keycloak client made public | ||
| - Renamed `cozypkg` to `cozyhr` |
There was a problem hiding this comment.
Typo in the component name. It should be cozy-hr (Helm Runner).
| - Renamed `cozypkg` to `cozyhr` | |
| - Renamed cozypkg to cozy-hr |
There was a problem hiding this comment.
Actionable comments posted: 4
♻️ Duplicate comments (14)
content/en/blog/2025-01-17-cozystack-v0-23.md (1)
9-9:⚠️ Potential issue | 🟡 MinorFix heading level jump at Line 9 (
###→##).The top in-body heading should be
##to keep hierarchy valid and satisfy MD001.Suggested fix
-### Cozystack v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM Instance Hooks, and Flux Operator Update +## Cozystack v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM Instance Hooks, and Flux Operator Update🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2025-01-17-cozystack-v0-23.md` at line 9, Change the in-body heading "Cozystack v0.23: Talos Linux v1.9.2, Telegram Alert Severity, VM Instance Hooks, and Flux Operator Update" from level 3 (###) to level 2 (##) so the document heading hierarchy is valid (fix MD001) — update the heading token at that line accordingly.content/en/blog/2024-08-31-cozystack-v0-13.md (1)
9-9:⚠️ Potential issue | 🟡 MinorNormalize first in-content heading at Line 9 to
##.
###here skips heading level and triggers MD001.Suggested fix
-### Cozystack v0.13: VictoriaLogs, VM Live Migration, KubeVirt v1.3, and Bridge Networking +## Cozystack v0.13: VictoriaLogs, VM Live Migration, KubeVirt v1.3, and Bridge Networking🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-08-31-cozystack-v0-13.md` at line 9, Change the in-content heading "### Cozystack v0.13: VictoriaLogs, VM Live Migration, KubeVirt v1.3, and Bridge Networking" to use an H2 (replace the leading "###" with "##") so the first in-content heading is normalized (fixes MD001); update the line containing that exact heading string.content/en/blog/2024-05-10-cozystack-v0-5.md (1)
9-9:⚠️ Potential issue | 🟡 MinorUse
##for the first post heading at Line 9.The first heading after frontmatter is
###, which skips heading level and triggers MD001.Suggested fix
-### Cozystack v0.5: Automatic Schema Generation, Cilium v1.14.10, and MariaDB Operator Update +## Cozystack v0.5: Automatic Schema Generation, Cilium v1.14.10, and MariaDB Operator Update🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-05-10-cozystack-v0-5.md` at line 9, The first content heading after the frontmatter uses a level-3 heading ("### Cozystack v0.5: Automatic Schema Generation, Cilium v1.14.10, and MariaDB Operator Update") which violates MD001; change that heading to a level-2 heading ("## ...") so the first post heading is `##` immediately after the frontmatter (locate the heading line containing that exact title and replace the leading "###" with "##").content/en/blog/2024-04-18-cozystack-v0-3.md (1)
9-9:⚠️ Potential issue | 🟡 MinorCorrect Line 9 heading level to
##.First post heading starts at
###, which violates MD001.Suggested fix
-### Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal Support +## Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal Support🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-04-18-cozystack-v0-3.md` at line 9, The blog post's main heading "Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal Support" is using level 3 (###); change it to level 2 (##) to comply with MD001 rule by updating the heading markup in that line (the heading string "Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal Support") so the first post-level heading is `##` instead of `###`.content/en/blog/2024-05-16-cozystack-v0-6.md (1)
9-9:⚠️ Potential issue | 🟡 MinorSet the first content heading to
##at Line 9.
###here skips a level and causes MD001.Suggested fix
-### Cozystack v0.6: VM Serial Console, Ephemeral Storage for Containers, and etcd Auto-Quota +## Cozystack v0.6: VM Serial Console, Ephemeral Storage for Containers, and etcd Auto-Quota🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-05-16-cozystack-v0-6.md` at line 9, The top-level content heading "### Cozystack v0.6: VM Serial Console, Ephemeral Storage for Containers, and etcd Auto-Quota" should be demoted to a second-level heading to avoid skipping heading levels (MD001); replace the leading "###" with "##" for that heading line so it becomes "## Cozystack v0.6: VM Serial Console, Ephemeral Storage for Containers, and etcd Auto-Quota".content/en/blog/2024-04-05-cozystack-v0-2.md (1)
9-9:⚠️ Potential issue | 🟡 MinorUse
##for the first in-body heading at Line 9.Current
###causes a heading level jump (MD001).Suggested fix
-### Cozystack v0.2: Bundles, Schema Versioning, FluxCD as Core Package, and Component Updates +## Cozystack v0.2: Bundles, Schema Versioning, FluxCD as Core Package, and Component Updates🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-04-05-cozystack-v0-2.md` at line 9, The in-body top-level heading "Cozystack v0.2: Bundles, Schema Versioning, FluxCD as Core Package, and Component Updates" is using ### which causes a heading level jump (MD001); change that heading token from ### to ## so it becomes a second-level heading (use "## Cozystack v0.2: Bundles, Schema Versioning, FluxCD as Core Package, and Component Updates") to correct the markdown hierarchy.content/en/blog/2024-09-16-cozystack-v0-15.md (1)
9-9:⚠️ Potential issue | 🟡 MinorAdjust Line 9 heading to
##to fix MD001.First body heading should not start at
###.Suggested fix
-### Cozystack v0.15: OpenCost, Talos Metal Image, Backup Fixes, and Kamaji OOM Fix +## Cozystack v0.15: OpenCost, Talos Metal Image, Backup Fixes, and Kamaji OOM Fix🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-09-16-cozystack-v0-15.md` at line 9, The first body heading "Cozystack v0.15: OpenCost, Talos Metal Image, Backup Fixes, and Kamaji OOM Fix" uses a level-3 heading (###); change it to a level-2 heading (##) so the document's first body heading is `##` and MD001 is resolved by replacing "### Cozystack v0.15: OpenCost, Talos Metal Image, Backup Fixes, and Kamaji OOM Fix" with "## Cozystack v0.15: OpenCost, Talos Metal Image, Backup Fixes, and Kamaji OOM Fix".content/en/blog/2025-04-10-cozystack-v0-30.md (1)
9-9:⚠️ Potential issue | 🟡 MinorFix the heading level to follow Markdown hierarchy.
The heading should use
##(h2) instead of###(h3) to maintain proper document structure. Markdown headings should increment by one level at a time.📝 Proposed fix for heading structure
-### Cozystack v0.30: GPU Passthrough, WorkloadMonitor for PVCs and IPs, CPUManager, and Automated Testing in CI +## Cozystack v0.30: GPU Passthrough, WorkloadMonitor for PVCs and IPs, CPUManager, and Automated Testing in CI🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2025-04-10-cozystack-v0-30.md` at line 9, The heading "Cozystack v0.30: GPU Passthrough, WorkloadMonitor for PVCs and IPs, CPUManager, and Automated Testing in CI" is currently level h3 (###); change it to level h2 (##) so the Markdown heading hierarchy increments correctly after the top-level title — update the heading text in the file content to use "##" instead of "###".content/en/blog/2025-10-10-cozystack-v0-37.md (2)
9-9:⚠️ Potential issue | 🟡 MinorFix heading level to maintain proper hierarchy.
The first content heading uses
###(h3), skipping h2. This violates MD001. Change to##for correct heading sequence.Proposed fix
-### Cozystack v0.37: OpenAPI Dashboard, Lineage Webhook, PVC Expansion in Tenants, and SeaweedFS S3 Discovery +## Cozystack v0.37: OpenAPI Dashboard, Lineage Webhook, PVC Expansion in Tenants, and SeaweedFS S3 Discovery🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2025-10-10-cozystack-v0-37.md` at line 9, The top-level content heading currently uses an h3 ("### Cozystack v0.37: OpenAPI Dashboard, Lineage Webhook, PVC Expansion in Tenants, and SeaweedFS S3 Discovery") which skips h2 and violates MD001; change the heading from "###" to "##" so the file's heading hierarchy is correct (update the heading text line in content/en/blog/2025-10-10-cozystack-v0-37.md to use "##" instead of "###").
4-4:⚠️ Potential issue | 🟠 MajorCorrect the publication date to match the actual v0.37.0 release date.
The date field is set to 2025-10-10, but v0.37.0 was released in early November 2025. Update the date to align with the actual release date to maintain accurate chronology.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2025-10-10-cozystack-v0-37.md` at line 4, The frontmatter date value is incorrect for the v0.37.0 release; update the single "date:" field in the post (the date key in this file) from 2025-10-10 to the actual release date in early November 2025 (e.g., 2025-11-??) so the blog post for v0.37.0 reflects the correct publication date.content/en/blog/2024-05-29-cozystack-v0-7.md (1)
9-9:⚠️ Potential issue | 🟡 MinorFix heading level jump at the post title heading.
Line 9 starts at
###, which skips the expected first content heading level and triggers MD001. Use##for the top in-body heading.Proposed fix
-### Cozystack v0.7: Network Stabilization, DNS Fixes, etcd Autocompaction, and cozy.local Domain +## Cozystack v0.7: Network Stabilization, DNS Fixes, etcd Autocompaction, and cozy.local Domain🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-05-29-cozystack-v0-7.md` at line 9, The post title heading uses level ### which skips expected top in-body heading and triggers MD001; update the heading for "Cozystack v0.7: Network Stabilization, DNS Fixes, etcd Autocompaction, and cozy.local Domain" by changing the leading hashes from ### to ## so the first content heading is at H2 level and resolves the markdown lint error.content/en/blog/2024-07-04-cozystack-v0-8.md (1)
9-9:⚠️ Potential issue | 🟡 MinorFix top-level heading level to avoid MD001.
The first in-body heading should be
##, not###, to keep heading increments valid.Proposed fix
-### Cozystack v0.8: FluxCD Operator, E2E Tests, ARM Support, and Managed Cluster Extensions +## Cozystack v0.8: FluxCD Operator, E2E Tests, ARM Support, and Managed Cluster Extensions🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-07-04-cozystack-v0-8.md` at line 9, The top-level in-body heading "Cozystack v0.8: FluxCD Operator, E2E Tests, ARM Support, and Managed Cluster Extensions" is using `###` which triggers MD001; change that heading from `###` to `##` so the first in-body heading is level 2 and heading increments are valid.content/en/blog/2024-07-23-cozystack-v0-10.md (1)
9-9:⚠️ Potential issue | 🟡 MinorUse an H2 for the first content heading.
###at the first heading level triggers MD001; change it to##.Proposed fix
-### Cozystack v0.10: FerretDB, NATS, Network Policies for Tenant Isolation, and etcd Operator v0.4 +## Cozystack v0.10: FerretDB, NATS, Network Policies for Tenant Isolation, and etcd Operator v0.4🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-07-23-cozystack-v0-10.md` at line 9, The first content heading "Cozystack v0.10: FerretDB, NATS, Network Policies for Tenant Isolation, and etcd Operator v0.4" uses a level-3 markdown header (###) which triggers MD001; change that header to a level-2 header (##) so the first content heading is H2, keeping the exact text unchanged.content/en/blog/2024-05-06-cozystack-v0-4.md (1)
9-9:⚠️ Potential issue | 🟡 MinorFix heading level jump at Line 9 (
###→##).This triggers markdownlint MD001 (heading increment). Start the first content heading at
##so subsequent levels remain sequential.Suggested fix
-### Cozystack v0.4: etcd Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix +## Cozystack v0.4: etcd Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-05-06-cozystack-v0-4.md` at line 9, The heading "Cozystack v0.4: etcd Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix" is using a level-3 marker (###) which causes a heading-level jump; change that heading marker from "###" to "##" so the first content heading starts at level 2 and subsequent headings remain sequential (locate the heading text "Cozystack v0.4: etcd Operator, Replica Options, Kamaji v0.5, and Dark Mode Fix" and replace the leading "###" with "##").
🧹 Nitpick comments (1)
content/en/blog/2024-05-06-cozystack-v0-4.md (1)
32-34: Consider varying sentence structure in the Fixes section.Three consecutive items start with "Fixed," which may reduce readability. Consider rephrasing one or two for variety, though this is a minor stylistic preference.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/en/blog/2024-05-06-cozystack-v0-4.md` around lines 32 - 34, The three bullet points in the Fixes section all start with "Fixed," which is repetitive; vary sentence structure by rewording one or two items (e.g., change one to "Tolerates kubectl edits in Flux," another to "Dashboard now uses correct dark-mode colors," or "Improved Kubernetes chart tolerations, datastore creation ordering, and topology spread constraints") so the list reads more smoothly while preserving the same meaning.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@content/en/blog/2024-09-04-cozystack-v0-14.md`:
- Line 9: The heading "Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users
and VHosts, and CNPG v1.24" is using ### and should be promoted to a level-2
heading (##) to fix the MD001 hierarchy error; update that heading in the file
so it reads "## Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and
VHosts, and CNPG v1.24" to restore proper markdown heading order.
In `@content/en/blog/2025-11-25-cozystack-v0-38.md`:
- Line 9: The first content heading "Cozystack v0.38: Virtual Private Cloud, VNC
Console, Configurable Worker K8s Versions, and HTTPS Enforcement" is using an h3
(###) and should be h2 to maintain proper Markdown hierarchy; update the heading
marker from `###` to `##` so the document starts with an h2 and resolves the
MD001 lint error.
In `@content/en/blog/2025-12-23-cozystack-v0-39.md`:
- Line 9: The top-level content heading "Cozystack v0.39: Topology-Aware
Routing, Windows VM Scheduling, Talm Overhaul, and VMAgent for Tenants"
currently uses a `###` (h3) and should be `##` (h2) to fix MD001; update the
markdown heading token from `###` to `##` so the document starts with the proper
h2-level heading and restores correct heading hierarchy.
In `@content/en/blog/2026-01-10-cozystack-v0-40.md`:
- Line 9: The top content heading "Cozystack v0.40: LINSTOR Scheduler, SeaweedFS
Traffic Locality, ValuesFrom Configuration, and Platform Decomposition" is using
### (h3) and triggers MD001; change that heading to an h2 by replacing the
leading "###" with "##" so the document starts with a proper h2 heading.
---
Duplicate comments:
In `@content/en/blog/2024-04-05-cozystack-v0-2.md`:
- Line 9: The in-body top-level heading "Cozystack v0.2: Bundles, Schema
Versioning, FluxCD as Core Package, and Component Updates" is using ### which
causes a heading level jump (MD001); change that heading token from ### to ## so
it becomes a second-level heading (use "## Cozystack v0.2: Bundles, Schema
Versioning, FluxCD as Core Package, and Component Updates") to correct the
markdown hierarchy.
In `@content/en/blog/2024-04-18-cozystack-v0-3.md`:
- Line 9: The blog post's main heading "Cozystack v0.3: Kafka, ClickHouse, and
Hetzner Bare-Metal Support" is using level 3 (###); change it to level 2 (##) to
comply with MD001 rule by updating the heading markup in that line (the heading
string "Cozystack v0.3: Kafka, ClickHouse, and Hetzner Bare-Metal Support") so
the first post-level heading is `##` instead of `###`.
In `@content/en/blog/2024-05-06-cozystack-v0-4.md`:
- Line 9: The heading "Cozystack v0.4: etcd Operator, Replica Options, Kamaji
v0.5, and Dark Mode Fix" is using a level-3 marker (###) which causes a
heading-level jump; change that heading marker from "###" to "##" so the first
content heading starts at level 2 and subsequent headings remain sequential
(locate the heading text "Cozystack v0.4: etcd Operator, Replica Options, Kamaji
v0.5, and Dark Mode Fix" and replace the leading "###" with "##").
In `@content/en/blog/2024-05-10-cozystack-v0-5.md`:
- Line 9: The first content heading after the frontmatter uses a level-3 heading
("### Cozystack v0.5: Automatic Schema Generation, Cilium v1.14.10, and MariaDB
Operator Update") which violates MD001; change that heading to a level-2 heading
("## ...") so the first post heading is `##` immediately after the frontmatter
(locate the heading line containing that exact title and replace the leading
"###" with "##").
In `@content/en/blog/2024-05-16-cozystack-v0-6.md`:
- Line 9: The top-level content heading "### Cozystack v0.6: VM Serial Console,
Ephemeral Storage for Containers, and etcd Auto-Quota" should be demoted to a
second-level heading to avoid skipping heading levels (MD001); replace the
leading "###" with "##" for that heading line so it becomes "## Cozystack v0.6:
VM Serial Console, Ephemeral Storage for Containers, and etcd Auto-Quota".
In `@content/en/blog/2024-05-29-cozystack-v0-7.md`:
- Line 9: The post title heading uses level ### which skips expected top in-body
heading and triggers MD001; update the heading for "Cozystack v0.7: Network
Stabilization, DNS Fixes, etcd Autocompaction, and cozy.local Domain" by
changing the leading hashes from ### to ## so the first content heading is at H2
level and resolves the markdown lint error.
In `@content/en/blog/2024-07-04-cozystack-v0-8.md`:
- Line 9: The top-level in-body heading "Cozystack v0.8: FluxCD Operator, E2E
Tests, ARM Support, and Managed Cluster Extensions" is using `###` which
triggers MD001; change that heading from `###` to `##` so the first in-body
heading is level 2 and heading increments are valid.
In `@content/en/blog/2024-07-23-cozystack-v0-10.md`:
- Line 9: The first content heading "Cozystack v0.10: FerretDB, NATS, Network
Policies for Tenant Isolation, and etcd Operator v0.4" uses a level-3 markdown
header (###) which triggers MD001; change that header to a level-2 header (##)
so the first content heading is H2, keeping the exact text unchanged.
In `@content/en/blog/2024-08-31-cozystack-v0-13.md`:
- Line 9: Change the in-content heading "### Cozystack v0.13: VictoriaLogs, VM
Live Migration, KubeVirt v1.3, and Bridge Networking" to use an H2 (replace the
leading "###" with "##") so the first in-content heading is normalized (fixes
MD001); update the line containing that exact heading string.
In `@content/en/blog/2024-09-16-cozystack-v0-15.md`:
- Line 9: The first body heading "Cozystack v0.15: OpenCost, Talos Metal Image,
Backup Fixes, and Kamaji OOM Fix" uses a level-3 heading (###); change it to a
level-2 heading (##) so the document's first body heading is `##` and MD001 is
resolved by replacing "### Cozystack v0.15: OpenCost, Talos Metal Image, Backup
Fixes, and Kamaji OOM Fix" with "## Cozystack v0.15: OpenCost, Talos Metal
Image, Backup Fixes, and Kamaji OOM Fix".
In `@content/en/blog/2025-01-17-cozystack-v0-23.md`:
- Line 9: Change the in-body heading "Cozystack v0.23: Talos Linux v1.9.2,
Telegram Alert Severity, VM Instance Hooks, and Flux Operator Update" from level
3 (###) to level 2 (##) so the document heading hierarchy is valid (fix MD001) —
update the heading token at that line accordingly.
In `@content/en/blog/2025-04-10-cozystack-v0-30.md`:
- Line 9: The heading "Cozystack v0.30: GPU Passthrough, WorkloadMonitor for
PVCs and IPs, CPUManager, and Automated Testing in CI" is currently level h3
(###); change it to level h2 (##) so the Markdown heading hierarchy increments
correctly after the top-level title — update the heading text in the file
content to use "##" instead of "###".
In `@content/en/blog/2025-10-10-cozystack-v0-37.md`:
- Line 9: The top-level content heading currently uses an h3 ("### Cozystack
v0.37: OpenAPI Dashboard, Lineage Webhook, PVC Expansion in Tenants, and
SeaweedFS S3 Discovery") which skips h2 and violates MD001; change the heading
from "###" to "##" so the file's heading hierarchy is correct (update the
heading text line in content/en/blog/2025-10-10-cozystack-v0-37.md to use "##"
instead of "###").
- Line 4: The frontmatter date value is incorrect for the v0.37.0 release;
update the single "date:" field in the post (the date key in this file) from
2025-10-10 to the actual release date in early November 2025 (e.g., 2025-11-??)
so the blog post for v0.37.0 reflects the correct publication date.
---
Nitpick comments:
In `@content/en/blog/2024-05-06-cozystack-v0-4.md`:
- Around line 32-34: The three bullet points in the Fixes section all start with
"Fixed," which is repetitive; vary sentence structure by rewording one or two
items (e.g., change one to "Tolerates kubectl edits in Flux," another to
"Dashboard now uses correct dark-mode colors," or "Improved Kubernetes chart
tolerations, datastore creation ordering, and topology spread constraints") so
the list reads more smoothly while preserving the same meaning.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 16a5c8ec-5232-4ae7-aed1-2f0279eb122a
📒 Files selected for processing (22)
content/en/blog/2024-02-20-cozystack-v0-1.mdcontent/en/blog/2024-04-05-cozystack-v0-2.mdcontent/en/blog/2024-04-18-cozystack-v0-3.mdcontent/en/blog/2024-05-06-cozystack-v0-4.mdcontent/en/blog/2024-05-10-cozystack-v0-5.mdcontent/en/blog/2024-05-16-cozystack-v0-6.mdcontent/en/blog/2024-05-29-cozystack-v0-7.mdcontent/en/blog/2024-07-04-cozystack-v0-8.mdcontent/en/blog/2024-07-10-cozystack-v0-9.mdcontent/en/blog/2024-07-23-cozystack-v0-10.mdcontent/en/blog/2024-08-21-cozystack-v0-12.mdcontent/en/blog/2024-08-31-cozystack-v0-13.mdcontent/en/blog/2024-09-04-cozystack-v0-14.mdcontent/en/blog/2024-09-16-cozystack-v0-15.mdcontent/en/blog/2024-12-04-cozystack-v0-19.mdcontent/en/blog/2025-01-17-cozystack-v0-23.mdcontent/en/blog/2025-04-10-cozystack-v0-30.mdcontent/en/blog/2025-10-10-cozystack-v0-37.mdcontent/en/blog/2025-11-25-cozystack-v0-38.mdcontent/en/blog/2025-12-23-cozystack-v0-39.mdcontent/en/blog/2026-01-10-cozystack-v0-40.mdcontent/en/blog/2026-01-20-cozystack-v0-41.md
✅ Files skipped from review due to trivial changes (5)
- content/en/blog/2024-08-21-cozystack-v0-12.md
- content/en/blog/2024-07-10-cozystack-v0-9.md
- content/en/blog/2024-02-20-cozystack-v0-1.md
- content/en/blog/2024-12-04-cozystack-v0-19.md
- content/en/blog/2026-01-20-cozystack-v0-41.md
| description: "Cozystack v0.14 adds automatic password generation for PostgreSQL, ClickHouse, and FerretDB, introduces user and vhost management for RabbitMQ, and updates CNPG to v1.24." | ||
| --- | ||
|
|
||
| ### Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24 |
There was a problem hiding this comment.
Fix heading hierarchy at Line 9 (### should be ##).
The first heading after frontmatter currently skips one level (MD001).
Suggested fix
-### Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24
+## Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24 | |
| ## Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24 |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2024-09-04-cozystack-v0-14.md` at line 9, The heading
"Cozystack v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG
v1.24" is using ### and should be promoted to a level-2 heading (##) to fix the
MD001 hierarchy error; update that heading in the file so it reads "## Cozystack
v0.14: Auto-Generated Passwords, RabbitMQ Users and VHosts, and CNPG v1.24" to
restore proper markdown heading order.
| description: "Cozystack v0.38 introduces Virtual Private Cloud with Multus CNI, VNC console for VMs in the dashboard, configurable Kubernetes worker versions, and HTTPS-only enforcement for the API." | ||
| --- | ||
|
|
||
| ### Cozystack v0.38: Virtual Private Cloud, VNC Console, Configurable Worker K8s Versions, and HTTPS Enforcement |
There was a problem hiding this comment.
Correct heading level to follow Markdown hierarchy.
Line 9 uses ### (h3) for the first content heading, which skips h2 and triggers MD001. Update to ## to maintain proper incremental heading structure.
Proposed fix
-### Cozystack v0.38: Virtual Private Cloud, VNC Console, Configurable Worker K8s Versions, and HTTPS Enforcement
+## Cozystack v0.38: Virtual Private Cloud, VNC Console, Configurable Worker K8s Versions, and HTTPS Enforcement📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.38: Virtual Private Cloud, VNC Console, Configurable Worker K8s Versions, and HTTPS Enforcement | |
| ## Cozystack v0.38: Virtual Private Cloud, VNC Console, Configurable Worker K8s Versions, and HTTPS Enforcement |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2025-11-25-cozystack-v0-38.md` at line 9, The first content
heading "Cozystack v0.38: Virtual Private Cloud, VNC Console, Configurable
Worker K8s Versions, and HTTPS Enforcement" is using an h3 (###) and should be
h2 to maintain proper Markdown hierarchy; update the heading marker from `###`
to `##` so the document starts with an h2 and resolves the MD001 lint error.
| description: "Cozystack v0.39 adds Cilium topology-aware routing, Windows VM scheduling with nodeAffinity, a major Talm tool overhaul with encryption support, and VMAgent for tenant namespace metrics." | ||
| --- | ||
|
|
||
| ### Cozystack v0.39: Topology-Aware Routing, Windows VM Scheduling, Talm Overhaul, and VMAgent for Tenants |
There was a problem hiding this comment.
Fix heading level to maintain proper hierarchy.
The first content heading uses ### (h3), skipping h2. This violates MD001. Change to ## to establish the correct heading sequence.
Proposed fix
-### Cozystack v0.39: Topology-Aware Routing, Windows VM Scheduling, Talm Overhaul, and VMAgent for Tenants
+## Cozystack v0.39: Topology-Aware Routing, Windows VM Scheduling, Talm Overhaul, and VMAgent for Tenants📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.39: Topology-Aware Routing, Windows VM Scheduling, Talm Overhaul, and VMAgent for Tenants | |
| ## Cozystack v0.39: Topology-Aware Routing, Windows VM Scheduling, Talm Overhaul, and VMAgent for Tenants |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2025-12-23-cozystack-v0-39.md` at line 9, The top-level
content heading "Cozystack v0.39: Topology-Aware Routing, Windows VM Scheduling,
Talm Overhaul, and VMAgent for Tenants" currently uses a `###` (h3) and should
be `##` (h2) to fix MD001; update the markdown heading token from `###` to `##`
so the document starts with the proper h2-level heading and restores correct
heading hierarchy.
| description: "Cozystack v0.40 introduces the LINSTOR scheduler for optimal pod placement near storage replicas, SeaweedFS traffic locality, a new ValuesFrom configuration mechanism, and major platform architecture refactoring." | ||
| --- | ||
|
|
||
| ### Cozystack v0.40: LINSTOR Scheduler, SeaweedFS Traffic Locality, ValuesFrom Configuration, and Platform Decomposition |
There was a problem hiding this comment.
Fix heading level jump at the first content heading.
Line 9 starts at ###, which triggers MD001 (expected h2; actual h3). Use ## here to keep a valid increment sequence.
Proposed fix
-### Cozystack v0.40: LINSTOR Scheduler, SeaweedFS Traffic Locality, ValuesFrom Configuration, and Platform Decomposition
+## Cozystack v0.40: LINSTOR Scheduler, SeaweedFS Traffic Locality, ValuesFrom Configuration, and Platform Decomposition📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Cozystack v0.40: LINSTOR Scheduler, SeaweedFS Traffic Locality, ValuesFrom Configuration, and Platform Decomposition | |
| ## Cozystack v0.40: LINSTOR Scheduler, SeaweedFS Traffic Locality, ValuesFrom Configuration, and Platform Decomposition |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 9-9: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/en/blog/2026-01-10-cozystack-v0-40.md` at line 9, The top content
heading "Cozystack v0.40: LINSTOR Scheduler, SeaweedFS Traffic Locality,
ValuesFrom Configuration, and Platform Decomposition" is using ### (h3) and
triggers MD001; change that heading to an h2 by replacing the leading "###" with
"##" so the document starts with a proper h2 heading.
1 participant
Summary
Details
These releases were identified by cross-referencing all major releases on github.com/cozystack/cozystack with existing blog posts on cozystack.io/blog. The already covered versions (v0.11, v0.16–v0.18, v0.20–v0.22, v0.24–v0.29, v0.31–v0.36, v1.0–v1.2) were not duplicated.
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit