I recently installed ArgoCD using a long manifest file, and I'm looking to shift to a Helm deployment. I noticed that the manifest is currently using the 'latest' tag, which isn't ideal. My first step is to pin a specific version, but I'm uncertain which one to choose. The GitHub releases show that the latest stable version is 3.2.0, but when I check the server it displays version 3.3.0. Is this a development version? Here's what I see when I run the command for the version:
```
$ argocd version
argocd: v3.1.5+cfeed49
BuildDate: 2025-09-10T16:01:20Z
GitCommit: cfeed4910542c359f18537a6668d4671abd3813b
GitTreeState: clean
GoVersion: go1.24.6
Compiler: gc
Platform: linux/amd64
argocd-server: v3.3.0+6cfef6b
```
What am I missing here, and what's the best way to set an image tag?
1 Answer
Just a heads up, the manifest itself doesn't actually use the 'latest' tag. It’s likely that you just didn’t check out a specific tag before you pulled the manifest. If you want the 3.2.0 version, here’s the manifest link:
[3.2.0 Manifest](https://raw.githubusercontent.com/argoproj/argo-cd/refs/tags/v3.2.0/manifests/install.yaml)
Got it. So basically the versioning issue is just about not switching to the right tag? Can you explain the difference in versions a bit more?