NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #113 by repository stars
Last release 1 years ago
23 Sep 2025
Ships unpredictably
gaps range from 8 days to 3.2 years
Most releases are documented
notes for 49 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
5232 releases · first in 2018
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release contains a critical security fix. Please refer to the security document for more information.
This release contains a critical security fix. Please refer to the security document for more information.
fix: correctly replace cache in namespace isolation mode
Nothing published for this version
fix: impossible to config RBAC if group name includes ','
Nothing published for this version
Nothing published for this version
The v1.4.0 is a stability release that brings multiple bug fixes, security, performance enhancements, and multiple usability improvements.
The v1.4.0 is a stability release that brings multiple bug fixes, security, performance enhancements, and multiple usability improvements.
A number of security enhancements and features have been implemented (thanks to @jannfis for driving it! ):
With the namespace isolation feature, you are no longer have to give full read-only cluster access to the Argo CD. Instead, you can give access only to selected namespaces with-in the cluster:
argocd cluster add <mycluster> --namespace <mynamespace1> --namespace <mynamespace2>
This feature is useful if you don't have full cluster access but still want to use Argo CD to manage some cluster namespaces. The feature also improves performance if Argo CD is used to manage a few namespaces of a large cluster.
The Argo CD no longer fork/exec kubectl to apply resource changes in the target cluster or convert resource manifest to the required manifest version. This reduces
CPU and Memory usage of large Argo CD instances.
The existing Argo CD resource hooks feature allows running custom logic during the syncing process. You can mark
any Kubernetes resource as a hook and Argo CD assess hook status if resource is a Pod, Job or Argo Workflow. In the v1.4.0 release Argo CD is going to leverage resource
health assessment to get sync hook status. This allows using any custom CRD as a sync hook and leverage custom health
check logic.
.gitmodules directory.argocd account can-i sync applications '*'The team put more effort into building tools that help to maintain Argo CD itself:
argocd-util allows to add and remove permissions defined in multiple project roles using one command.More documentation and tools are coming in patch releases.
The Argo CD deletes all in-flight hooks if you terminate running sync operation. The hook state assessment change implemented in this release the Argo CD enables detection of
an in-flight state for all Kubernetes resources including Deployment, PVC, StatefulSet, ReplicaSet etc. So if you terminate the sync operation that has, for example,
StatefulSet hook that is Progressing it will be deleted. The long-running jobs are not supposed to be used as a sync hook and you should consider using
Sync Waves instead.
argocd auth can-i command. Close #2255argocd app create in CLI if --revision is omitted #2665Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
- #2819 Fixes logging of tracing option in CLI
Nothing published for this version
- #2721 High CPU utilisation (5 cores) and spammy logs
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
- #2797 Fix directory traversal edge case and enhance tests
Nothing published for this version
Nothing published for this version
Nothing published for this version
- #2664 update account password from API resulted 404 - #2724 Can't use DNS-1123 compliant app name when creating project role - #2726 App list does n
DNS-1123 compliant app name when creating project roleNothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Too many vulnerabilities in Docker image
We know that for many of our users, they want to deploy existing Helm charts using Argo CD. Up until now that has required you to create an Argo CD app in a Git repo that does nothing but point to that chart. Now you can use a Helm chart repository is the same way as a Git repository.
On top of that, we've improved support for Helm apps. The most common types of Helm hooks such as pre-install and post-install are supported as well as a the delete policy before-hook-creation which makes it easier to work with hooks.
https://youtu.be/GP7xtrnNznw
Some users would like to make sure that resources in a namespace are managed only by Argo CD. So we've introduced the concept of an "orphan resource" - any resource that is in namespace associated with an app, but not managed by Argo CD. This is enabled in the project settings. Once enabled, Argo CD will show in the app view any resources in the app's namespace that is not managed by Argo CD.
https://youtu.be/9ZoTevVQf5I
There may be instances when you want to control the times during which an Argo CD app can sync. Sync Windows now gives you the capability to create windows of time in which apps are either allowed or denied the ability to sync. This can apply to both manual and auto-sync, or just auto-sync. The windows are configured at the project level and assigned to apps using app name, namespace or cluster. Wildcards are supported for all fields.
argocd.argoproj.io/hook-delete-policy: BeforeHookCreation (#2036)helm template --kube-version (#2275)group optional for ignoreDifferences config (#2298)Dockerfile to use the hack/install.sh (#2488)TestHookDeleteBeforeCreation (#2141)* * * * * schedule (#2475)Required Pruning (#2577)argocd version in the self-building container image (#2645)action/* (#2670)kubectl-parallelism-limit flag is broken (#2673)Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →