Skip to content

docs(release): add changelog for v1.4.0 - #2675

Merged
myasnikovdaniil merged 3 commits into
mainfrom
changelog-v1.4.0
May 19, 2026
Merged

myasnikovdaniil merged 3 commits into
mainfrom
changelog-v1.4.0

Conversation

@myasnikovdaniil

@myasnikovdaniil myasnikovdaniil commented May 19, 2026 •

Copy link
Copy Markdown
Contributor

This PR adds the changelog for release v1.4.0.

✅ Changelog has been automatically generated in docs/changelogs/v1.4.0.md.

Summary by CodeRabbit

  • Documentation
    • Released v1.4.0 changelog describing a redesigned schema-driven dashboard, persistent tenant storage, unified instance-type presets, declarative multi-database backups, optional fractional GPU sharing, and PROXY-protocol support
    • Includes upgrade guidance, operator timing knobs, kubelet/autoscaler behavior changes, security fixes, component version bumps, and full changelog link

Review Change Stack

Signed-off-by: Myasnikov Daniil <[email protected]>
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces the official changelog documentation for the Cozystack v1.4.0 release. It provides a detailed overview of the significant platform enhancements, including the new dashboard UI, persistent worker node storage, instance-type resource presets, and declarative backup strategies, alongside critical dependency updates and bug fixes.

Highlights

  • Release v1.4.0 Changelog: Added the comprehensive changelog for the v1.4.0 release, detailing major features, platform component updates, bug fixes, and upgrade instructions.
New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment Gemini (@gemini-code-assist) Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

@github-actions github-actions Bot added size/L This PR changes 100-499 lines, ignoring generated files area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) labels May 19, 2026
@coderabbitai

coderabbitai Bot commented May 19, 2026 •

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: dee9429e-f9c1-4a8f-8223-472c68dd2a5e

📥 Commits

Reviewing files that changed from the base of the PR and between b2c9efd and 0ca1014.

📒 Files selected for processing (1)
  • docs/changelogs/v1.4.0.md
✅ Files skipped from review due to trivial changes (1)
  • docs/changelogs/v1.4.0.md

📝 Walkthrough

Walkthrough

This PR adds the v1.4.0 release changelog documenting feature highlights, upgrade notes, platform component updates, major improvements, bug fixes, security/configuration notes, dependency updates, documentation changes, and contributor acknowledgements.

Changes

v1.4.0 Release Changelog

Layer / File(s) Summary
Release summary and feature highlights
docs/changelogs/v1.4.0.md
Document header and release intro; Feature Highlights covering dashboard Kubernetes-API frontend rewrite, persistent tenant worker-node storage, instance-type preset taxonomy with Migration 39, declarative backup strategies, optional HAMi GPU sharing, PROXY-protocol support and ouroboros NAT fix, per-Application HelmRelease timeout control, and kubelet allocatable-based reporting; includes Upgrade Notes and Required Actions.
Platform components, improvements, fixes, and security
docs/changelogs/v1.4.0.md
Platform Components section listing upstream version bumps (Talos, cert-manager, Cilium, GPU Operator, etc.); Major Features and Improvements summarizing platform, app, networking, and operator changes; Bug Fixes covering reconciliation/race fixes and chart/controller corrections; Security and System Configuration items including proxyProtocol approach and cert-manager UID notes.
Dependencies, development changes, documentation, and contributors
docs/changelogs/v1.4.0.md
Dependencies & Version Updates; Development, Testing, and CI/CD workflow changes; Documentation updates (instance presets, publishing/proxyProtocol, GPU sharing guides, website/in-repo docs); Contributors and New Contributors list with Full Changelog compare link.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

area/release

Suggested reviewers

  • lexfrei
  • androndo
  • sircthulhu
  • lllamnyp
  • IvanHunters

Poem

🐰 I hopped in with notes for v1.4,
Dashboards polished, storage and more,
Backups set and GPUs to share,
Proxy fixed with careful care,
Contributors nibble carrots, encore!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs(release): add changelog for v1.4.0' clearly and specifically describes the main change: adding release notes documentation for version 1.4.0. It is concise, uses conventional commit format, and accurately represents the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch changelog-v1.4.0

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces the comprehensive changelog for Cozystack v1.4.0, detailing major updates such as the new schema-driven dashboard UI, persistent worker node storage, and a cloud-style resource preset taxonomy. Feedback from the review identifies several typos in CVE identifiers and feature gate names that need correction. Additionally, the PR violates repository style guidelines regarding the PR title scope and the missing mandatory release-note block in the description.

Comment thread docs/changelogs/v1.4.0.md
@@ -0,0 +1,358 @@
<!--

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The pull request does not adhere to the repository's contribution guidelines:

  1. Invalid Scope: The PR title docs(release): ... uses release as a scope, which is not in the list of valid scopes defined in the Repository Style Guide (lines 40-45). Consider using docs(docs) or docs(meta).
  2. Missing Release Note: The PR description lacks the mandatory release-note block required by the Repository Style Guide (lines 51-57).
References
  1. PR title must follow Conventional Commits with valid scopes. (link)
  2. PR body must contain a release-note block. (link)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The docs(release): title and body match the CI-generated changelog PR exactly (see .github/workflows/tags.yaml lines 428-429, which creates the same PR automatically on tag push). release is a recognized scope: .github/workflows/pr-labeler.yaml maps it to area/release, and the scope list in docs/agents/contributing.md is explicitly non-exhaustive ("examples — not an exhaustive list; pick the most specific scope"). Changelog-bundling PRs ARE the release notes and do not carry an additional release-note block by repo convention.

Comment thread docs/changelogs/v1.4.0.md

## Platform Components

* **Talos**: v1.12.7 → v1.13.0 (v1.12.7 was the final v1.3.x step, shipped in v1.3.2 via #2547 for CVE-2026-31431). v1.13.0 ships a Clang-built kernel with ThinLTO optimization, enables Container Device Interface by default for dynamic device-spec files under `/run/cdi`, adds a new `talosctl debug` subcommand for attaching to privileged debug containers, introduces the `EnvironmentConfig` document that replaces and deprecates `.machine.env`, adds virtiofs-based external volumes via `ExternalVolumeConfig`, machine-wide container-image signature verification via `ImageVerificationConfig`, and a new `LifecycleService` API for programmatic installs and upgrades. Component updates: Linux 6.18.24, containerd 2.2.3, etcd 3.6.9, CoreDNS 1.14.2, Kubernetes 1.36.0, CNI 1.9.1, runc 1.4.2, systemd 259.5. Built with Go 1.26.2. ([release notes](https://github.com/siderolabs/talos/releases/tag/v1.13.0)) ([**@kvaps**](https://github.com/kvaps) in #2546)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Typo in CVE ID: CVE-2026-31431 should be CVE-2024-31431 to correctly reference the vulnerability fixed in Talos v1.12.7.

Suggested change
* **Talos**: v1.12.7 → v1.13.0 (v1.12.7 was the final v1.3.x step, shipped in v1.3.2 via #2547 for CVE-2026-31431). v1.13.0 ships a Clang-built kernel with ThinLTO optimization, enables Container Device Interface by default for dynamic device-spec files under `/run/cdi`, adds a new `talosctl debug` subcommand for attaching to privileged debug containers, introduces the `EnvironmentConfig` document that replaces and deprecates `.machine.env`, adds virtiofs-based external volumes via `ExternalVolumeConfig`, machine-wide container-image signature verification via `ImageVerificationConfig`, and a new `LifecycleService` API for programmatic installs and upgrades. Component updates: Linux 6.18.24, containerd 2.2.3, etcd 3.6.9, CoreDNS 1.14.2, Kubernetes 1.36.0, CNI 1.9.1, runc 1.4.2, systemd 259.5. Built with Go 1.26.2. ([release notes](https://github.com/siderolabs/talos/releases/tag/v1.13.0)) ([**@kvaps**](https://github.com/kvaps) in #2546)
* **Talos**: v1.12.7 → v1.13.0 (v1.12.7 was the final v1.3.x step, shipped in v1.3.2 via #2547 for CVE-2024-31431). v1.13.0 ships a Clang-built kernel with ThinLTO optimization, enables Container Device Interface by default for dynamic device-spec files under `/run/cdi`, adds a new `talosctl debug` subcommand for attaching to privileged debug containers, introduces the `EnvironmentConfig` document that replaces and replaces and deprecates `.machine.env`, adds virtiofs-based external volumes via `ExternalVolumeConfig`, machine-wide container-image signature verification via `ImageVerificationConfig`, and a new `LifecycleService` API for programmatic installs and upgrades. Component updates: Linux 6.18.24, containerd 2.2.3, etcd 3.6.9, CoreDNS 1.14.2, Kubernetes 1.36.0, CNI 1.9.1, runc 1.4.2, systemd 259.5. Built with Go 1.26.2. ([release notes](https://github.com/siderolabs/talos/releases/tag/v1.13.0)) ([**@kvaps**](https://github.com/kvaps) in #2546)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CVE ID is correct. The original Talos bump PR #2545 carries CVE-2026-31431 in its title, body, and release-note block, and the Siderolabs blog at siderolabs.com/blog/exploit-fail-cve-2026-31431-copy-fail-barely-scratches-talos-linux uses the same identifier. CVE-2024-31431 is unrelated.

Comment thread docs/changelogs/v1.4.0.md

* **[security] Bump Go dependencies to clear Dependabot CVE alerts**: Bumps root module Go deps to latest, kubeovn-webhook, kubevirt-csi-driver, token-proxy, and `api/apps/v1alpha1` deps, plus the OpenTelemetry exporter modules to align with the otel core; first-party Dockerfile builders are bumped to `golang:1.26`, and the first-party scratch images now run as non-root UID 65532. `USER 65532` is dropped from `cozystack-api` and `lineage-controller-webhook` containers in favor of the OCI-level UID so it can be overridden by PodSecurityContext ([**@lexfrei**](https://github.com/lexfrei) in #2494).

* **[talos] Bump Talos to v1.12.7 (CVE-2026-31431)**: See Platform Components — picks up the kernel fix for the "Copy Fail" local privilege escalation in `algif_aead` *(backported to v1.3.2 via #2547)* ([**@kvaps**](https://github.com/kvaps) in #2545).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Typo in CVE ID: CVE-2026-31431 should be CVE-2024-31431.

Suggested change
* **[talos] Bump Talos to v1.12.7 (CVE-2026-31431)**: See Platform Components — picks up the kernel fix for the "Copy Fail" local privilege escalation in `algif_aead` *(backported to v1.3.2 via #2547)* ([**@kvaps**](https://github.com/kvaps) in #2545).
* **[talos] Bump Talos to v1.12.7 (CVE-2024-31431)**: See Platform Components — picks up the kernel fix for the "Copy Fail" local privilege escalation in `algif_aead` *(backported to v1.3.2 via #2547)* ([**@kvaps**](https://github.com/kvaps) in #2545).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as the other thread: CVE-2026-31431 is the actual identifier used by Siderolabs and by the original bump PR #2545. No change needed.

Comment thread docs/changelogs/v1.4.0.md Outdated

* **KubeVirt**: v1.6.3 → v1.8.2. Two-minor jump crossing the upstream QEMU bump — VMs running before the upgrade need a cold restart (see Upgrade Notes). New CRD fields for changed block tracking (storage-agnostic incremental backups), `s390x` support added, `ppc64le` deprecated. The standalone ServiceMonitor / alerts templates are removed in favour of the Helm-rendered PrometheusRule. ([v1.7.0 notes](https://github.com/kubevirt/kubevirt/releases/tag/v1.7.0), [v1.8.0 notes](https://github.com/kubevirt/kubevirt/releases/tag/v1.8.0)) ([**@IvanHunters**](https://github.com/IvanHunters) in #2502)
- **VM Backup API + Changed Block Tracking** — new alpha `VMBackup` resource and `ChangedBlockTracking` matcher on `KubeVirt` enable storage-agnostic incremental backups; CBT also applies to hotplug volumes; libvirt checkpoints survive VM restart for resumable incremental flows.
- **Confidential VMs (experimental)**: Intel TDX support behind the `WorkloadEncryptionTDX` feature gate, AMD SEV-SNP behind `WorkloadEncruptionSEV` (alongside the existing SEV/SEV-ES paths).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

Typo in the feature gate name: WorkloadEncruptionSEV should be WorkloadEncryptionSEV.

Suggested change
- **Confidential VMs (experimental)**: Intel TDX support behind the `WorkloadEncryptionTDX` feature gate, AMD SEV-SNP behind `WorkloadEncruptionSEV` (alongside the existing SEV/SEV-ES paths).
- **Confidential VMs (experimental)**: Intel TDX support behind the `WorkloadEncryptionTDX` feature gate, AMD SEV-SNP behind `WorkloadEncryptionSEV` (alongside the existing SEV/SEV-ES paths).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 025f4e4. Verified against upstream source: the actual feature gate in kubevirt/kubevirt:pkg/virt-config/featuregate/active.go is WorkloadEncryptionSEV. The misspelling came from quoting the v1.7.0 release-notes text verbatim — corrected to match the real gate name so users can copy-paste it.

Comment thread docs/changelogs/v1.4.0.md Outdated

* **[docs/operations] Resource presets reference**: New `docs/operations/resource-presets.md` in-repo doc documenting the new five-series taxonomy and the legacy alias mapping ([**@lexfrei**](https://github.com/lexfrei) in #2607).

* **[talm] Release v0.25.0, v0.25.1, v0.26.0, v0.26.1, v0.27.0, v0.28.0, v0.28.1, v0.28.2** (github.com/cozystack/talm): The talm CLI gains apply-time safety gates (declared-resource existence + drift preview/verify), a wrapper UX overhaul (persistent flags, `-n` drop, crashdump, kubeconfig hint, dmesg cushion, TUI refusal), META preservation by default on `talm reset`, a pre-flight Talos version check on `apply`, multi-NIC discovery for chart defaults (filtered to IPv4 family, longest-prefix VIP-link matching), strict golangci-lint config + cross-platform CI gates, `--image` flag on `init`, cluster-name overrides via `dislogical`, and a handful of charts/engine fixes (RotateKeys atomic rotation, IPv6 bracket normalisation, `$patch:delete` no-op on absent paths). Notable PRs: ([**@lexfrei**](https://github.com/lexfrei) in cozystack/talm#127, #128, #129, #130, #133, #135, #136, #145, #146, #149, #150, #154, #158, #160, #161, #162, #163, #173, #197, #199, #200, #201, #202; [**@dislogical**](https://github.com/dislogical) in cozystack/talm#148).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

For consistency with other contributor mentions in this document, consider using the formatted username for @dislogical.

Suggested change
* **[talm] Release v0.25.0, v0.25.1, v0.26.0, v0.26.1, v0.27.0, v0.28.0, v0.28.1, v0.28.2** (github.com/cozystack/talm): The talm CLI gains apply-time safety gates (declared-resource existence + drift preview/verify), a wrapper UX overhaul (persistent flags, `-n` drop, crashdump, kubeconfig hint, dmesg cushion, TUI refusal), META preservation by default on `talm reset`, a pre-flight Talos version check on `apply`, multi-NIC discovery for chart defaults (filtered to IPv4 family, longest-prefix VIP-link matching), strict golangci-lint config + cross-platform CI gates, `--image` flag on `init`, cluster-name overrides via `dislogical`, and a handful of charts/engine fixes (RotateKeys atomic rotation, IPv6 bracket normalisation, `$patch:delete` no-op on absent paths). Notable PRs: ([**@lexfrei**](https://github.com/lexfrei) in cozystack/talm#127, #128, #129, #130, #133, #135, #136, #145, #146, #149, #150, #154, #158, #160, #161, #162, #163, #173, #197, #199, #200, #201, #202; [**@dislogical**](https://github.com/dislogical) in cozystack/talm#148).
* **[talm] Release v0.25.0, v0.25.1, v0.26.0, v0.26.1, v0.27.0, v0.28.0, v0.28.1, v0.28.2** (github.com/cozystack/talm): The talm CLI gains apply-time safety gates (declared-resource existence + drift preview/verify), a wrapper UX overhaul (persistent flags, `-n` drop, crashdump, kubeconfig hint, dmesg cushion, TUI refusal), META preservation by default on `talm reset`, a pre-flight Talos version check on `apply`, multi-NIC discovery for chart defaults (filtered to IPv4 family, longest-prefix VIP-link matching), strict golangci-lint config + cross-platform CI gates, `--image` flag on `init`, cluster-name overrides via **@dislogical**, and a handful of charts/engine fixes (RotateKeys atomic rotation, IPv6 bracket normalisation, `$patch:delete` no-op on absent paths). Notable PRs: ([**@lexfrei**](https://github.com/lexfrei) in cozystack/talm#127, #128, #129, #130, #133, #135, #136, #145, #146, #149, #150, #154, #158, #160, #161, #162, #163, #173, #197, #199, #200, #201, #202; [**@dislogical**](https://github.com/dislogical) in cozystack/talm#148).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 0ca1014 using the linked-contributor format [**@dislogical**](https://github.com/dislogical) that the rest of the changelog uses for contributor mentions.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/changelogs/v1.4.0.md`:
- Around line 102-103: Replace the misspelled KubeVirt feature gate name
`WorkloadEncruptionSEV` with the correct `WorkloadEncryptionSEV` in the
changelog entry so users can copy-paste the exact feature flag; update the
second bullet where `WorkloadEncruptionSEV` appears (alongside
`WorkloadEncryptionTDX`) to the correct spelling.
🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 780307e7-fd63-4f39-a266-060c6a26a41b

📥 Commits

Reviewing files that changed from the base of the PR and between d0c12c6 and b2c9efd.

📒 Files selected for processing (1)
  • docs/changelogs/v1.4.0.md

Comment thread docs/changelogs/v1.4.0.md Outdated
Address review feedback from gemini-code-assist on
docs/changelogs/v1.4.0.md:102 and coderabbitai on :103: the AMD
SEV-SNP feature gate in upstream KubeVirt source is WorkloadEncryptionSEV
(see pkg/virt-config/featuregate/active.go), not WorkloadEncruptionSEV
as quoted from the v1.7.0 release notes.

Signed-off-by: Myasnikov Daniil <[email protected]>
Address review feedback from gemini-code-assist on
docs/changelogs/v1.4.0.md:326: the in-prose mention of dislogical was
rendered as inline code rather than as a contributor link. Switch to
the [**@user**](https://github.com/user) format used elsewhere in the
changelog.

Signed-off-by: Myasnikov Daniil <[email protected]>
@myasnikovdaniil
myasnikovdaniil merged commit f6f34cb into main May 19, 2026
10 checks passed
@myasnikovdaniil
myasnikovdaniil deleted the changelog-v1.4.0 branch May 19, 2026 10:40
Andrei Kvapil (kvaps) added a commit that referenced this pull request May 20, 2026
## What this PR does

Follow-up to #2675. Fixes four broken references in
`docs/changelogs/v1.4.0.md` that were caught by re-verifying every link
in the merged changelog:

| Where | Was | Now |
|---|---|---|
| Resource Presets doc link (Feature Highlights) |
`cozystack.io/docs/operations/resource-presets/` (404) |
`cozystack.io/docs/v1.4/guides/resource-management/` |
| HAMi doc link (Feature Highlights) |
`cozystack.io/docs/operations/kubernetes/hami/` (404) |
`cozystack.io/docs/v1.4/kubernetes/gpu-sharing/` |
| Upgrade notes — resource presets PR ref | `#2426` (`feat(monitoring):
upgrade victoria-metrics-operator`) | `#2607` (`feat(apps):
instance-type resource presets`) |
| Upgrade notes — postgres parameters PR ref | `#2475` (unrelated open
issue about bundle YAML) | `#2466` (`feat(postgres)!: support all
PostgreSQL configuration parameters`) |

The Feature Highlights / Major Features sections already cited #2607 and
#2466 correctly; only the Upgrade Notes section pointed at the wrong PR
numbers.

### Release note

```release-note
NONE
```

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Updated changelog documentation links to reflect new resource
management guides location.
* Refreshed HAMi compatibility references to point to current
GPU-sharing documentation.
  * Updated related PR references in upgrade notes for accuracy.

<!-- review_stack_entry_start -->

[![Review Change
Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/cozystack/cozystack/pull/2693?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack)

<!-- review_stack_entry_end -->

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) automated Created by automation kind/documentation Categorizes issue or PR as related to documentation size/L This PR changes 100-499 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants