Argo CD v3.5.0 released on 04-08-2026
Argo CD v3.5.0 is out now. Operators and GitOps teams get signed container images and provenance (SLSA Level 3) plus a broad set of feature, UX and stability improvements that aim to make upgrades and day‑to‑day operation safer and more predictable.
See the Argo CD GitHub release, the operator documentation for installation guidance and signature verification, and the full changelog for a detailed list of changes.
What’s in this release
- Quick start and upgrade guidance with one‑line kubectl installs for Non‑HA and HA deployments (apply install.yaml or ha/install.yaml into the argocd namespace).
- Signed releases and provenance: all container images are signed with cosign and generated provenance meets SLSA Level 3; documentation is provided for verifying signatures and provenance.
- Major features and UX work including configurable jitter for webhook‑triggered refreshes, ApplicationSet concurrency and UI improvements (preview, resource tree and per‑app banners), Source Hydrator promotion and Source Integrity opt‑ins, Helm 4 migration and glob support for valueFiles, and expanded health checks and resource actions.
Upgrade notes
- If you are upgrading between minor versions, read the official upgrading documentation before you proceed: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/.
- There are no special rollback instructions in the release notes; consult the full changelog and the upgrade guide for steps and report any problems on the Argo CD GitHub if you need help: https://github.com/argoproj/argo-cd/compare/v3.4.6…v3.5.0.
Tell the project and other users how the upgrade went — open an issue or leave feedback on the Argo CD GitHub release if you run into problems or have observations to share.
