Argo CD v3.6.1 released on 04-11-2026
Argo CD v3.6.1 is out now. It provides simple installation commands for single-instance and high-availability deployments, ships signed container images with cosign and SLSA Level 3 provenance, and backports targeted UI fixes for the 3.6 branch.
See the project GitHub release, the operator documentation and the release blog for installation commands, verification steps and the full changelog.
What’s in this release
- Quick Start & Install (Non‑HA and HA): create the argocd namespace and apply the release manifests server-side with force-conflicts. Example commands:
kubectl create namespace argocdandkubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.6.1/manifests/install.yaml(useha/install.yamlat the same v3.6.1 path for HA). - Release Signatures & Provenance: all Argo CD container images are signed with cosign and provenance is produced meeting SLSA Level 3 for container images and CLI binaries; verification guidance is provided in the signed-release-assets documentation.
- Bug fixes & UI improvements: cherry-picked front-end fixes for 3.6 — keep the sidebar layout in sync after toggling and stop webpack minifying index.html so
--rootpath/--basehrefwork correctly. Full changelog: https://github.com/argoproj/argo-cd/compare/v3.6.0…v3.6.1
Upgrade notes
- If you’re moving between minor versions, consult the upgrading documentation for compatibility and migration steps: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/
- Release metadata and assets are available at https://api.github.com/repos/argoproj/argo-cd/releases/latest — use those assets to locate previous tags if you need to roll back.
Share your experience with v3.6.1 and any upgrade notes or issues you encounter in the project’s community channels or issue tracker.
