You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Manifest diff shows all resources as recreated after upgrade to 2.1.0 #672
After upgrading helm-dashboard from 2.0.4 to 2.1.0, the Manifest changes
dialog (current.yaml → upgraded.yaml) shows all Kubernetes resources as
newly created instead of showing only the actual diff.
Steps to Reproduce
Install helm-dashboard 2.1.0
Open any deployed Helm release
Click "Upgrade" and select a new chart version
Open the "Manifest changes" tab
Expected Behavior
Only changed resources/fields are highlighted (as in v2.0.4).
Actual Behavior
All resources are shown as new additions — as if the current release has
no manifest at all.
Root Cause (bisected)
The /api/helm/releases/<ns>/<name>/manifests endpoint returns text/plain
YAML. In v2.1.0, useGetReleaseManifest was switched from fetchWithDefaults
to fetchWithSafeDefaults (frontend/src/API/releases.ts).
fetchWithSafeDefaults treats any string response as an error and returns
the fallback value ([]):
if (typeof data === "string") {
console.error(url, " response is string");
return fallback; // returns [] instead of the YAML string
}
As a result, the current manifest is passed to the /diff endpoint as an
empty string (a=""), so the diff shows every resource as a new addition.
Fix
In frontend/src/API/releases.ts, revert useGetReleaseManifest to use
fetchWithDefaults instead of fetchWithSafeDefaults, since this endpoint
intentionally returns text/plain and not JSON.
Activity
fix: manifest diff shows all resources as recreated (#672)
fix: manifest diff shows all resources as recreated (#672) (#673)
undera commentedon Mar 27, 2026
Thanks for reporting it! I released 2.1.1 with the fix
east4ming commentedon Mar 29, 2026
I encountered the same problem. Now I dare not upgrade the helm chart through Helm-Dashboard, fearing the introduction of unknown accidents.
undera commentedon Mar 29, 2026
The issue were purely in frontend presentation of empty diff, no backend Helm logic was involved.