Argo CD v3.4.6 released on 31-07-2026
Argo CD v3.4.6 is out now. It supplies immediate install commands for single‑instance and HA deployments, signed container images and provenance meeting SLSA Level 3, and a set of cherry‑picked bug fixes useful to operators and CI/CD administrators.
For the manifests, signature verification steps and full details see the Quick Start manifests on GitHub, the signed‑release‑assets documentation (readthedocs) and the full changelog linked in the release notes.
What’s in this release
- Quick Start: immediate install commands for Non‑HA and HA — apply the v3.4.6 manifests into the argocd namespace (install.yaml for Non‑HA; ha/install.yaml for HA).
- Signed release assets 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; verification documentation provided.
- Notable bug fixes and improvements: a set of cherry‑picked fixes including AppSet fallback to create when patch returns NotFound, preserving manager‑owned descendant fields during webhook mutation filtering, Helm registry passwords passed via stdin, mounting argocd-cmd-params-cm in repo-server to enable pprof, selective annotation backfill, progressive sync fixes, Entra ID UTI claim handling when jti is absent, and using OIDC refresh tokens to renew expired sessions.
Upgrade notes
- If upgrading across minor versions, read the official upgrading guide before you start: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/
- There are no special rollback instructions in these release notes; consult the full changelog and the release comparison for details: https://github.com/argoproj/argo-cd/compare/v3.4.5…v3.4.6
Share your experience with v3.4.6 — whether the upgrade went smoothly or you hit snags — so others in the community can learn from it.
