helmfile release-level continueOnError keeps independent releases processing
Introduced 2026-09-30 · score 0.98
HOW TO USE IT
When syncing releases, set `continueOnError: true` on releases whose failures should not stop independent DAG branches. Helmfile skips dependent releases and exits non-zero if any release fails.
releases:
- name: app-a
chart: ./charts/app-a
continueOnError: true
- name: app-b
chart: ./charts/app-b
continueOnError: true
helmfile synchelmfile sync --file <path/to/helmfile.yaml>WHY THIS HELPS
Continue syncing independent releases after a release fails while deploying a Helmfile release set.
BEFORE THIS CHANGE
By default, `helmfile sync` stops on the first release failure (fail-fast).
REQUIREMENTS AND LIMITATIONS
- Version: v1.8.1
- continueOnError: Release-level boolean; defaults to false. When true, Helmfile continues independent releases after this release fails; releases depending on it are skipped. Does not change Helm rollback behavior or make the command succeed.
- sync (required): Helmfile subcommand that syncs cluster state from the Helmfile.
- --file: Path to the Helmfile YAML state; defaults to `helmfile.yaml`.
- The setting defaults to false.
- Only independent releases continue; releases that depend on a failed release are skipped.
- The command exits non-zero when any release fails.
- For apply, diff and chart-preparation failures remain fatal and are not converted into tolerated release errors.
- Helm's per-release rollback behavior and other existing Helm behavior are unchanged.
FIRST-PARTY EVIDENCE
- https://github.com/helmfile/helmfile/releases/tag/v1.8.1
- https://github.com/helmfile/helmfile/pull/2804
- https://github.com/helmfile/helmfile/blob/v1.8.1/docs/configuration.md
- https://github.com/helmfile/helmfile/blob/v1.8.1/docs/cli.md
- https://github.com/helmfile/helmfile/blob/v1.8.1/docs/releases.md
Check the installed version and the source before using it. Entry JSON