Skip to content

chore(deps): update dependency argoproj/argo-cd to v3#964

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

chore(deps): update dependency argoproj/argo-cd to v3#964
renovate[bot] wants to merge 1 commit intomainfrom
renovate/argoproj-argo-cd-3.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 6, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
argoproj/argo-cd major v2.14.21v3.3.7

Release Notes

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

v3.3.7

Compare Source

v3.3.6

Compare Source

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.6/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.6/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

Full Changelog: argoproj/argo-cd@v3.3.5...v3.3.6

v3.3.5

Compare Source

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.5/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.5/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.4...v3.3.5

v3.3.4

Compare Source

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.4/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.4/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
Other work

Full Changelog: argoproj/argo-cd@v3.3.3...v3.3.4

v3.3.3

Compare Source

[!IMPORTANT]
Following Helm 3.19.0 change in how Helm interprets K8s cluster version, Argo CD 3.3.3 release contains a change that aligns how Argo CD interprets K8s cluster version with Helm behavior.

Impact: Application Sets with Cluster Generators, that fetch clusters based on their Kubernetes version and use argocd.argoproj.io/auto-label-cluster-info on the cluster secret, need to be updated to use argocd.argoproj.io/kubernetes-version with the vMajor.Minor.Patch format instead of the previous Major.Minor format.

More details here: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#cluster-version-format-change

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.3/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.3/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
Other work

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

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, 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

@renovate renovate Bot requested a review from a team as a code owner May 6, 2025 12:56
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch 2 times, most recently from 0f57e87 to a5addc3 Compare May 19, 2025 19:57
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch 2 times, most recently from 1f4c9ae to 4f97df0 Compare May 28, 2025 20:35
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 4f97df0 to c9f504c Compare May 29, 2025 20:55
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from c9f504c to b7eadb2 Compare June 10, 2025 03:13
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from b7eadb2 to 58a6317 Compare July 12, 2025 16:13
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 58a6317 to 8f5bd07 Compare July 25, 2025 22:58
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 8f5bd07 to f77db17 Compare August 14, 2025 03:40
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from f77db17 to 30e4d43 Compare August 25, 2025 17:10
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch 4 times, most recently from 11b237a to e7ca903 Compare September 10, 2025 18:38
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch 2 times, most recently from 1f8d3bb to 5dda56f Compare September 23, 2025 01:20
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 5dda56f to 4887142 Compare September 30, 2025 18:39
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 4887142 to ff28002 Compare October 18, 2025 01:03
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from ff28002 to fb939e8 Compare November 4, 2025 17:49
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from fb939e8 to 10488ee Compare November 30, 2025 17:41
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch 3 times, most recently from 67bb952 to 644730c Compare December 18, 2025 13:40
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 644730c to f9da753 Compare December 24, 2025 16:25
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch 2 times, most recently from eb89dc4 to f3cce12 Compare January 14, 2026 17:56
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from f3cce12 to bd7861d Compare January 22, 2026 20:49
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from bd7861d to d72842f Compare February 2, 2026 14:35
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from d72842f to 7591a35 Compare February 18, 2026 14:28
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 7591a35 to a82f71d Compare February 22, 2026 17:21
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch 2 times, most recently from b9de646 to 1e51851 Compare March 16, 2026 14:36
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch 2 times, most recently from 89075c1 to 9f8d3a2 Compare March 27, 2026 17:03
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 9f8d3a2 to ec2a7ce Compare April 16, 2026 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants