Last checked and updated on 04 May 2026
What Is New in Helm 3.3 (summary table)
| Category | Highlights |
|---|---|
| New Features |
|
| Improvements |
|
| Bug Fixes |
|
| Security |
|
| Deprecated | None announced for this release |
How does Helm 3.3 improve release upgrades and rollbacks?
Helm now permits an upgrade of a release that previously failed, preventing you from being stuck in a broken state. The rollback logic was also refined to handle edge cases where no deployed version existed.
Why it matters
In practice this reduces manual cleanup and shortens the time to recover from transient errors during CI/CD pipelines.
What new linting capabilities does Helm 3.3 bring?
Linting now validates chart names, checks for missing selectors, and coalesces values before running value tests. Deprecation warnings are also surfaced during lint runs.
Why it matters
Early detection of naming and selector issues prevents failed deployments and keeps chart quality high across teams.
Which environment variables can I set to control Helm’s configuration location?
Helm 3.3 introduces variables that follow the XDG spec (e.g., XDG_CONFIG_HOME, XDG_CACHE_HOME) allowing you to relocate config, cache, and data directories without modifying command‑line flags.
Why it matters
This is handy for containerised builds or CI runners where the default home directory is read‑only.
What is the new HelmVersion field in Capabilities used for?
The HelmVersion attribute reports the client version to charts at render time, enabling conditional logic based on Helm features.
Why it matters
Chart authors can now write version‑aware templates, simplifying support for multiple Helm releases.
FAQ
Can I upgrade a release that previously failed?
Yes, Helm 3.3 adds support for upgrading a failed release directly, eliminating the need to manually delete or purge the release first.
How does the new linting behavior affect my CI pipelines?
Lint now merges supplied values before validation, so you can pass a values file and still get accurate name and selector checks without extra steps.
Which XDG environment variables does Helm respect?
Helm reads XDG_CONFIG_HOME, XDG_CACHE_HOME, and XDG_DATA_HOME to locate its configuration, cache, and data directories.
What does the HelmVersion field enable in charts?
Charts can query .Capabilities.HelmVersion to conditionally include resources or use syntax that only newer Helm versions support.
Are there any breaking changes I need to be aware of?
No deprecations were announced in 3.3, and existing commands retain their behavior; the release focuses on stability and new linting features.