diff --git a/src/content/release-notes.mdx b/src/content/release-notes.mdx
index 3aa9b0d13..f4bd3e304 100644
--- a/src/content/release-notes.mdx
+++ b/src/content/release-notes.mdx
@@ -16,9 +16,31 @@ Okteto Chart release 1.41 is designed to work with [Okteto CLI 3.16.x](https://g
 
 - **Build Queue System**: Okteto now implements a build queue system that ensures consistent build performance and fair resource distribution. Build requests are automatically routed to the optimal Okteto Build pod based on real-time metrics (CPU pressure, memory usage, and IOPS). When all build pods are busy, builds enter a queue and wait until resources become available, preventing overload and ensuring predictable build times. This behavior is enabled by default but can be disabled by setting the `OKTETO_BUILD_QUEUE_ENABLED` feature flag to `false` via [Admin Variables](admin/dashboard.mdx#admin-variables). Learn more about the [Build Queue System](core/build-service.mdx#build-queue-system)
 
+- **Helm 4 Support (Opt-in)**: Helm 4 is now available alongside Helm 3 for testing and validation. Helm 3 remains the default in this release. Helm 4 introduces server-side apply (SSA) as the default behavior, which changes how Kubernetes resources are created and tracked. Most charts will work without modifications. Test your deployments with Helm 4 before it becomes the default in Okteto 1.42.
+
+  **How to test Helm 4:**
+
+  Choose one of the following approaches:
+
+  **Option 1: Testing at the cluster level**
+  - Set the admin variable `OKTETO_HELM_4_ENABLED` to `true` in **Admin → Settings → Admin Variables**
+  - When enabled, all `helm` commands automatically use Helm 4 across the entire cluster
+  - To revert, set `OKTETO_HELM_4_ENABLED` to `false` or remove the admin variable `OKTETO_HELM_4_ENABLED`
+
+  **Option 2: Testing at the Development Environment level**
+  - Update your Okteto Manifest deploy commands to use `helm4` instead of `helm`. For example:
+    ```yaml
+    deploy:
+      - helm4 upgrade --install myapp ./chart
+    ```
+  - To revert, change `helm4` back to `helm` or use the `helm3` command explicitly
+
+  **Important**: Helm 4 will become the default Helm binary in **Okteto 1.42**. We recommend testing your deployments with Helm 4 now to ensure a smooth transition.
+
 ### Improvements {#improvements-1.41}
 
 - **Configurable Build Service Thresholds**: Administrators can now configure resource thresholds (CPU pressure, memory usage, and IOPS) directly from the [Build Service admin dashboard](admin/build-service.mdx) to fine-tune when build pods are considered busy
+- **Server-Side Apply Support**: The Okteto CLI now properly handles resources created via server-side apply (SSA), ensuring Helm 4-created resources are correctly grouped in the UI and cleanup operations work as expected
 
 ## 1.40.0