v1.3.0

A stability and hardening release. Five reviewed critical bug fixes (found in a code review, each verified empirically and independently cross-checked), plus cleaner logs and CI hardening. No breaking changes.

Highlights

• Plan export can no longer destroy files. The dangerous os.TempDir() fallback is gone, and export now validates the symlink-resolved plan dir — rejecting the filesystem root, top-level dirs, the cwd and the temp root, and defeating symlink / relative-TMPDIR bypasses — then stages atomically so a failed export always leaves the previous plan recoverable.
• No more crashes on bad graphs. A dependency cycle (A → B → A or A → A) used to stack-overflow before the cycle detector ran; it's now guarded. down no longer hangs forever when an uninstall failure strands a dependant.
• Race-free concurrency. Fixed a data race on the monitor-failures map and made failed-monitor remediation deterministic (the safer action wins — a release is never randomly deleted instead of rolled back). Concurrent registry logins are serialized so credentials can't mix or corrupt the shared store.
• Cleaner output. Log and CLI messages drop the decorative emoji for clear, greppable text (syncing releases, release deployed, plan has no changes).

Install

Binaries for linux and darwin (amd64/arm64), plus deb/rpm/apk packages, are attached below.

docker pull ghcr.io/semx/helmtide:1.3.0

---

Changelog

v1.2.0

helmtide is a maintained fork of helmwave, built on the Helm v4 SDK. This is the first release with written notes; it consolidates the Helm v4 line and hardens the test and release pipeline.

Highlights

• Helm v4 SDK. Helm v3 reaches end of life in November 2026; helmtide builds on v4 today, and exposes its new options: wait strategies (watcher, legacy, hookOnly), server_side_apply, force_conflicts, and post_render_strategy.
• OCI registries fixed. Per-chart plain_http and insecure are honored again — Helm v4 had ignored them on an injected registry client.
• Trustworthy CI. A hermetic, KinD-based integration suite runs on every pull request (rollback, hooks, http + prometheus monitors, post-render strategies, server-side vs client-side apply, plain-HTTP OCI). Suites that pull charts from third-party repos are gated behind HELMTIDE_TEST_REMOTE_CHARTS, so a chart-CDN outage can never turn CI red.

Install

Binaries for linux and darwin (amd64/arm64), plus deb/rpm/apk packages, are attached below.

# container image
docker pull ghcr.io/semx/helmtide:1.2.0

Upgrading from helmwave

helmtide tracks helmwave's config format. The one removal to be aware of on the Helm v4 line: recreate on a release is gone — Helm v4 removed the option it set.

---

Changelog

Breaking change!

• feat: build on helm v4 instead of helm v3, which reaches EOL in November 2026 (@semx)

• feat: drop recreate from a release, helm v4 removed the option it set (@semx)

New feature

• feat: wait also accepts a helm v4 wait strategy (watcher, legacy, hookOnly), and server_side_apply, force_conflicts and post_render_strategy expose the new helm v4 options (@semx)

Fixed

• fix: honor per-chart plain_http/insecure for OCI registries (helm v4 ignored them on an injected client) (@semx)

CI

• ci: kind-based integration gate on pull_request/push -- automated live-cluster tests for rollback, Helm hooks, http and prometheus monitors, post_render_strategy (combined/separate/nohooks), server-side vs client-side apply with force_conflicts, and plain-HTTP OCI (@semx)

• ci: gate the internet-dependent integration suites (bitnami, prometheus-community, ...) behind HELMTIDE_TEST_REMOTE_CHARTS so a third-party chart CDN outage can never fail CI; the hosted job stays hermetic (local charts + in-cluster registry) while the remote-chart regression is opt-in (@semx)

v1.1.0

Merge pull request #1 from semx/feat/helm-v4

Migrate to the Helm v4 SDK

v1.0.0

helmtide v1.0.0

First stable release of the fork, from helmwave v0.42.3.

Runs on Helm 4; upstream is on Helm 3, which loses support in November 2026.
No known vulnerabilities: govulncheck found 33 reachable in the inherited tree,
and moving to Helm 4 took the last of them out of the module graph. The
integration suite installs, diffs, rolls back and uninstalls real releases
against a live cluster, which is what 1.0 is claiming.

Breaking against helmwave: recreate: is gone, Helm 4 has no field behind it.
Everything else runs unchanged, including helmwave.yml and HELMWAVE_*.

The version starts at 1.0.0 rather than continuing helmwave's numbering, so a
helmtide release is never confused with the 0.43.0 upstream had planned.