Argo CD v3.6.1 released on 04-11-2026
Argo CD v3.6.1 is out now. Operators can install non‑HA or HA deployments immediately with the provided manifests, and published container images and CLI binaries include cosign signatures plus SLSA Level 3 provenance for supply‑chain verification.
See the project GitHub release, the operator documentation and the full changelog for installation, verification and upgrade details.
What’s in this release
- Quick start & installation: non‑HA and HA manifests are provided; run kubectl create namespace argocd and apply the manifests with server-side apply and –force-conflicts (non-HA: https://raw.githubusercontent.com/argoproj/argo-cd/v3.6.1/manifests/install.yaml, HA: https://raw.githubusercontent.com/argoproj/argo-cd/v3.6.1/manifests/ha/install.yaml).
- Release signatures & provenance: all Argo CD container images are signed with cosign and a provenance is produced for container images and CLI binaries meeting SLSA Level 3; verification steps are documented in the operator manual (https://argo-cd.readthedocs.io/en/stable/operator-manual/signed-release-assets).
- Bug fixes & UI fixes: cherry‑picked fixes for 3.6 include keeping the UI sidebar layout in sync after toggling and preventing webpack from minifying index.html so –rootpath/–basehref options work correctly (backported to the 3.6 branch).
Upgrade notes
- If you are upgrading between minor versions, read the upgrading guide before proceeding: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/.
- For rollbacks or to inspect exact changes, consult the full changelog and compare v3.6.0…v3.6.1: https://github.com/argoproj/argo-cd/compare/v3.6.0…v3.6.1.
Share your experience or any issues on the Argo CD project GitHub or community channels; feedback on the install flow and the UI fixes will help others planning the same upgrade.
