Argo CD v3.4.2 released on 12-05-2026
Argo CD v3.4.2 is out now. It provides clear install commands for both non‑HA and HA deployments from the release manifests, and strengthens supply‑chain integrity with signed container images and generated provenance metadata.
See the release manifests on GitHub and the Argo CD documentation for installation commands, signature and provenance verification, and full upgrade guidance.
What’s in this release
- Quick Start: non‑HA and HA install commands using server-side apply from the v3.4.2 manifests (kubectl create namespace argocd; kubectl apply -n argocd –server-side –force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.4.2/manifests/install.yaml and the HA equivalent manifest).
- Signed releases and provenance: all Argo CD container images are signed with cosign and provenance metadata is generated for images and CLI binaries meeting SLSA Level 3; documentation explains how to verify signatures and provenance.
- Bug fixes and runtime stability: cherry‑picked fixes include reverting an unnecessary UpdateRevisionForPaths change, preventing a panic when APIResource is nil in the permission validator, and applying HideSecretData to server‑side diff results for Secrets to avoid leaking secret data.
Upgrade notes
- No breaking changes are listed in the release notes; follow the official upgrading documentation for cross‑minor upgrades: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/
- Rollbacks: consult the full changelog (compare v3.4.1…v3.4.2) to identify relevant commits when diagnosing issues or planning a rollback: https://github.com/argoproj/argo-cd/compare/v3.4.1…v3.4.2
Share your experience with v3.4.2 on the Argo CD GitHub or community channels so others can see what worked and what didn’t.
