LoginSign Up
← Back to all sparks
H

Helm

INFRA · APIS
Velocity5.0

Package manager for Kubernetes applications

helm.sh ↗

Helm 3 ships its final minor release while Helm 4.3 eliminates multi-minute status computation delays.

kubernetespackage-managementdevtoolsend-of-lifeperformanceoci
◆Current state
Helm is running two parallel release trains. Helm 3.22.0, released alongside 4.3.0, is officially the last Helm 3 minor release — patch-only from here until end of life. Helm 4 is the active development path, with 4.3.0 delivering real performance work: concurrent status computation removes what were previously multi-minute stalls on large deployments. The consistent k8s-io group bumps across both branches reflect ongoing Kubernetes version alignment.
◆Where it's heading
With Helm 3 in maintenance, the team's attention fully consolidates on Helm 4. The 4.3.0 changes — concurrent status computation, ownership verification at uninstall, SOURCE_DATE_EPOCH support for reproducible archives — indicate that Helm 4 is prioritizing safety for GitOps and CI/CD workflows at scale. The resync period cut from 1 hour to 3 minutes points toward tighter reconciliation loops for teams running Helm as infrastructure management rather than one-shot deploy tooling.
◆Prediction
Helm 4.4.0 (scheduled January 2027) will likely continue hardening uninstall safety and improving OCI registry interactions. Helm 3 will receive security patches only — teams still on v3 should treat the end-of-life announcement as a migration deadline.

◆Recent moves

  1. 6d ago

    Helm 3.22.0: final minor release, deps and k8s-io 0.37.0

    Helm 3.22.0 is the final Helm 3 minor release — the release notes explicitly say 'primarily dependency updates and k8s-io group to 0.37.0,' with a single registry token-auth scope fix backported. No new capabilities; this is a maintenance close-out for the v3 branch.

    View source ↗
  2. 6d ago

    Helm 4.3.0: concurrent status, uninstall safety, reproducible archives

    Helm 4.3.0 brings concurrent status computation (eliminating multi-minute delays on large deployments), resource ownership verification before uninstall, SOURCE_DATE_EPOCH support for reproducible chart archives, and a rollback description flag for audit trails. These are practical workflow improvements for teams running Helm at scale in GitOps pipelines.

    View source ↗
  3. 15d ago

    Helm 3.22.0 RC1: staging candidate for final v3 minor

    Release candidate for Helm 3.22.0 — no notable changes listed, intended for staging validation before the final 3.x minor release. The RC itself carries no new functionality.

    View source ↗
  4. 15d ago

    Helm 4.3.0 RC1: staging candidate for 4.3 feature release

    Release candidate for Helm 4.3.0 — no notable changes listed in the RC itself; the feature work from 4.3.0 (concurrent status, uninstall ownership checks) was validated here before the stable release.

    View source ↗
  5. 1mo ago

    Helm 4.2.4: values file boundary fix, SSA retry, security patches

    Helm 4.2.4 patches a multi-container test log gap, a 4096-byte boundary bug in values file loading, server-side apply conflict retries, and two security advisories (gRPC GO-2026-6061, OTel GO-2026-5158). The registry credential retention fix on plain-HTTP fallback is the most operationally impactful for teams using token-authenticated registries.

    View source ↗
  6. 1mo ago

    Helm 3.21.4: security patches for four CVEs

    Helm 3.21.4 is a security-focused patch: four CVEs addressed (GO-2026-5932 via ProtonMail/go-crypto migration, GO-2026-5158, GO-2026-6061, GO-2026-5970 through crypto bumps), plus a panic fix on empty file template processing. Teams running self-managed Helm 3 installations should prioritize this upgrade.

    View source ↗