Skip to content

chore(deps): update dependency argoproj/argo-cd to v3.3.2#653

Open
renovate[bot] wants to merge 2 commits intomainfrom
renovate/argoproj-argo-cd-3.x
Open

chore(deps): update dependency argoproj/argo-cd to v3.3.2#653
renovate[bot] wants to merge 2 commits intomainfrom
renovate/argoproj-argo-cd-3.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 18, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
argoproj/argo-cd minor 3.1.83.3.2

Release Notes

argoproj/argo-cd (argoproj/argo-cd)

v3.3.2

Compare Source

[!IMPORTANT]
Before upgrading all types of Argo CD installations to this release, please read the upgrade guide first:
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

Upgrading Argo CD which is managing itself

Users who have an Argo CD Application that manages their Argo CD installation, must enable ServerSideApply=true sync option on this Application in order for the upgrade to succeed.

The issue with failed to perform client-side apply migration that existed on version 3.3.0 and 3.3.1 has been solved in this release: #​26279

For users who have previously upgraded to Argo CD 3.3.0or 3.3.1 and applied the temporary remediation of ClientSideApplyMigration=false sync option on the Application that manages their Argo CD, are required to remove this setting to restore the default behavior of performing the migration.
The reason for removing the ClientSideApplyMigration=false sync option is that it may cause conflicts between Argo CD K8s field manager and other field managers at a later point in time.

More details here:
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

Quick Start

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.2/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.2/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes
Documentation

Full Changelog: argoproj/argo-cd@v3.3.1...v3.3.2

v3.3.1

Compare Source

[!IMPORTANT]
Before upgrading all types of Argo CD installations to this release, please read the upgrade guide first:
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

Upgrading Argo CD which is managing itself

Users who have an Argo CD Application that manages their Argo CD installation, must enable ServerSideApply=true sync option on this Application in order for the upgrade to succeed.

In some cases, there may be a sync error like Failed to perform client-side apply migration: failed to perform client-side apply migration on manager kubectl-client-side-apply.

We are currently working on a long-term fix to this issue, the progress can be tracked here: #​26279

A temporary remediation is to additionally set the ClientSideApplyMigration=false sync option on this Application. This solution is temporary and not recommended for the long run because it may result in conflicts between Argo CD K8s field manager and other field managers at a later point in time, and if you use it, you will need to remove it after the above issue is fixed.

More details here:
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

Quick Start

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.1/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.1/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes
Dependency updates
Other work

Full Changelog: argoproj/argo-cd@v3.3.0...v3.3.1

v3.3.0

Compare Source

[!IMPORTANT]
Before upgrading all types of Argo CD installations to this release, please read the upgrade guide first:
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

Upgrading Argo CD which is managing itself

Users who have an Argo CD Application that manages their Argo CD installation, must enable ServerSideApply=true sync option on this Application in order for the upgrade to succeed.

In some cases, like when the self-managing of Argo CD is performed with Kustomize, there may be a sync error like Failed to perform client-side apply migration: failed to perform client-side apply migration on manager kubectl-client-side-apply.

We are currently working on a long-term fix to this issue, the progress can be tracked here: #​26279

A temporary remediation is to additionally set the ClientSideApplyMigration=false sync option on this Application. This solution is temporary and not recommended for the long run because it may result in conflicts between Argo CD K8s field manager and other field managers at a later point in time, and if you use it, you will need to remove it after the above issue is fixed.

More details here:
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

Quick Start

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.0/manifests/install.yaml
HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.0/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post.

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Features
Bug fixes

@renovate renovate bot added the dependency Dependency version related label Oct 18, 2025
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 2733eb8 to c029872 Compare October 22, 2025 14:51
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from eefce84 to 5087df8 Compare November 4, 2025 21:02
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.1.9 chore(deps): update dependency argoproj/argo-cd to v3.2.0 Nov 4, 2025
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 4b3bf90 to 3b63738 Compare November 10, 2025 23:40
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from ce7dfa2 to 29bb5ab Compare November 30, 2025 18:08
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.2.0 chore(deps): update dependency argoproj/argo-cd to v3.2.1 Nov 30, 2025
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 6a90090 to 8de3dd2 Compare December 10, 2025 15:43
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 7381db3 to 5e72ca6 Compare December 18, 2025 14:02
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.2.1 chore(deps): update dependency argoproj/argo-cd to v3.2.2 Dec 18, 2025
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 484ac6c to 667dffe Compare December 24, 2025 13:47
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.2.2 chore(deps): update dependency argoproj/argo-cd to v3.2.3 Dec 24, 2025
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from ac11347 to 8a9e905 Compare January 13, 2026 15:41
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.2.3 chore(deps): update dependency argoproj/argo-cd to v3.2.4 Jan 13, 2026
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 81605d8 to d79efda Compare January 14, 2026 17:41
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.2.4 chore(deps): update dependency argoproj/argo-cd to v3.2.5 Jan 14, 2026
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 30386ca to 4296ed9 Compare January 22, 2026 21:12
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.2.5 chore(deps): update dependency argoproj/argo-cd to v3.2.6 Jan 22, 2026
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from e8c26a5 to c5e2966 Compare February 2, 2026 09:36
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.2.6 chore(deps): update dependency argoproj/argo-cd to v3.3.0 Feb 2, 2026
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from ecab00b to 102ee78 Compare February 2, 2026 21:01
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 102ee78 to ead7d86 Compare February 18, 2026 13:33
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.3.0 chore(deps): update dependency argoproj/argo-cd to v3.3.1 Feb 18, 2026
@renovate renovate bot force-pushed the renovate/argoproj-argo-cd-3.x branch from c31a208 to 1821ecf Compare February 22, 2026 16:36
@renovate renovate bot changed the title chore(deps): update dependency argoproj/argo-cd to v3.3.1 chore(deps): update dependency argoproj/argo-cd to v3.3.2 Feb 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependency Dependency version related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant