Argo CD v3.4.2 released on 12-05-2026
Argo CD v3.4.2 is out now. Operators get immediate install commands for both non‑HA and HA deployments, and all container images and CLI binaries in the release are signed with cosign and accompanied by SLSA Level 3 provenance to support verification.
See the changelog, upgrading guide and verification documentation on the Argo CD GitHub and Read the Docs for full details and the exact install commands: https://github.com/argoproj/argo-cd/compare/v3.4.1…v3.4.2 and https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/ and https://argo-cd.readthedocs.io/en/stable/operator-manual/signed-release-assets
What’s in this release
- Quick Start commands for immediate installation: non‑HA via https://raw.githubusercontent.com/argoproj/argo-cd/v3.4.2/manifests/install.yaml and HA via https://raw.githubusercontent.com/argoproj/argo-cd/v3.4.2/manifests/ha/install.yaml using server-side apply with –force-conflicts.
- Signed releases and provenance: all container images signed with cosign and provenance metadata produced for images and CLI binaries meeting SLSA Level 3; verification documentation provided.
- Bug fixes and cherry‑picks backported to the 3.4 branch, including a revert of an unnecessary UpdateRevisionForPaths change, a fix to avoid panics when APIResource is nil in the permission validator, and ensuring gitops‑engine hides secret data in server‑side diffs for Secrets.
Upgrade notes
- No breaking changes are listed for v3.4.2; if you are upgrading between minor versions read the upgrading guide at https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/ before proceeding.
- If you must roll back, redeploy the previous tag (for example v3.4.1) and consult the changelog for differences: https://github.com/argoproj/argo-cd/compare/v3.4.1…v3.4.2
Share your experience with the new quick-start commands and signed releases — tell the project if anything in your upgrade or verification flow went unexpectedly.
