Argo CD v3.6.1 was published on November 4, 2026 as a patch release on the release 3.6 branch. The change that matters to operators is a fix for --rootpath and --basehref, which stopped working when webpack minified index.html. It is a stable release, not a prerelease.
The full release notes and downloads are on the GitHub release page.
The release contains two bug fixes and one version bump. Both fixes are in the web UI. There are no server, controller, or repo server changes listed. If you run Argo CD at the root of a hostname, this release changes very little for you. If you serve it under a path prefix, read on.
Subpath deployments and index.html minification ¶
The notable fix is commit abfc76157c9a9bcdc4b4161077e4e0e7993493fe, whose title says webpack should stop minifying index.html so --rootpath and --basehref work. It is a cherry pick of #30767 onto the 3.6 branch, tracked as #30768.
Argo CD lets you serve the UI under a prefix such as /argocd behind a shared ingress. The argocd-server flags --rootpath and --basehref control that. The server rewrites parts of index.html at startup so that asset and API paths carry the prefix. The commit title implies the minified output no longer left that file in a form the rewrite could handle. The release notes do not describe the exact mechanism, so treat that part as inference.
The practical symptom for an operator on a subpath would be a UI that loads with wrong asset paths, or not at all, while the API and the argocd CLI keep working. The fix is to leave index.html unminified in the build. The tradeoff is a slightly larger HTML file. The file is tiny, and the JavaScript bundles are unaffected by this change.
Who benefits:
- Teams that share one ingress host across several tools and route by path.
- Anyone who set
--rootpathor--basehrefonargocd-serverand held back from 3.6.0. - Platform teams that template these flags through Helm values or kustomize patches.
If you never set either flag, you are not exposed to this bug.
Sidebar layout state ¶
The second fix is commit 94037c4d4e1af4bd0651d37a179fbd9e347e668c. It keeps the sidebar layout in sync after toggling it. It is a cherry pick of #30762, landed on the 3.6 branch as #30771.
This one is cosmetic and UI local. It does not touch the data path, the Application CRD, or sync behavior. It is listed here because it is one of only two functional changes, not because it affects pipelines.
What is not in this release ¶
The remaining entry, c7c41d322fb1592b09c72448ac439abc3c69af48, bumps the version to 3.6.1 on the release 3.6 branch. That is release housekeeping.
The notes list no security fixes, no manifest changes, and no CRD changes. The standard install manifests are linked per tag, so the quick start commands in the release body point at v3.6.1 paths for both the non HA and HA layouts. They apply with --server-side and --force-conflicts.
The container images are signed with cosign. Provenance is generated for images and CLI binaries that meet SLSA Level 3. The release notes point to the signed release assets documentation for verification steps. If your admission policy verifies signatures, run that check before rolling the new tag.
Upgrade notes ¶
From v3.6.0, this is a patch bump with no documented migration steps. Review the compare view between v3.6.0 and v3.6.1 if you want the exact diff.
If you are coming from a different minor version, the release notes tell you to read the upgrading documentation first. Minor upgrades are where behavior changes live. This patch is not.
A sensible check after the rollout, if you use a subpath:
- Load the UI through the ingress path and confirm static assets return 200.
- Confirm the redirect after login lands under the prefix.
- Check that
argocd-serverstill has the same--rootpathand--basehrefvalues in its args.
Further details are on the release page.
Where to get it ¶
- Release page: https://github.com/argoproj/argo-cd/releases/tag/v3.6.1
- Repository: https://github.com/argoproj/argo-cd
- Tag:
v3.6.1