Skip to content

🤖 Update dependency argoproj/argo-cd to v3.3.9#102

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

🤖 Update dependency argoproj/argo-cd to v3.3.9#102
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 Aug 13, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
argoproj/argo-cd Kustomization minor v3.0.12v3.3.9

Release Notes

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

v3.3.9

Compare Source

v3.3.8

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.8/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.8/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.7...v3.3.8

v3.3.7

Compare Source

Quick Start

[!IMPORTANT]
A potential bug with application reconciliation has been identified in this release. The application controller may fail to refresh applications, causing an application to not sync / show resources as out of sync.

Issue: #​27344 – Application controller not refreshing applications

Non-HA:
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.7/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.7/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.6...v3.3.7

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

Note

PR body was truncated to here.

@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 443d1d8 to 411df82 Compare August 25, 2025 16:47
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.1.0 🤖 Update dependency argoproj/argo-cd to v3.1.1 Aug 25, 2025
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 411df82 to 58a7659 Compare September 4, 2025 17:40
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.1.1 🤖 Update dependency argoproj/argo-cd to v3.1.2 Sep 4, 2025
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 58a7659 to 0af91bc Compare September 4, 2025 21:06
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.1.2 🤖 Update dependency argoproj/argo-cd to v3.1.3 Sep 4, 2025
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 0af91bc to bfcf405 Compare September 5, 2025 21:49
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.1.3 🤖 Update dependency argoproj/argo-cd to v3.1.4 Sep 5, 2025
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from bfcf405 to 2ea3bc5 Compare September 10, 2025 16:32
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.1.4 🤖 Update dependency argoproj/argo-cd to v3.1.5 Sep 10, 2025
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 2ea3bc5 to f69c006 Compare September 18, 2025 21:14
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.1.5 🤖 Update dependency argoproj/argo-cd to v3.1.6 Sep 18, 2025
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from f69c006 to 810be9b Compare September 23, 2025 00:51
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.1.6 🤖 Update dependency argoproj/argo-cd to v3.1.7 Sep 23, 2025
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 810be9b to dd81faf Compare September 30, 2025 18:41
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.1.7 🤖 Update dependency argoproj/argo-cd to v3.1.8 Sep 30, 2025
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from dd81faf to c3c6ac4 Compare October 18, 2025 03:57
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.1.8 🤖 Update dependency argoproj/argo-cd to v3.1.9 Oct 18, 2025
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from c3c6ac4 to 6f1f576 Compare November 4, 2025 20:12
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.1.9 🤖 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 6f1f576 to 13ac1c8 Compare November 30, 2025 13:09
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.2.0 🤖 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 13ac1c8 to 40c4fe9 Compare December 18, 2025 15:04
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.2.1 🤖 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 40c4fe9 to e135b4a Compare December 24, 2025 12:41
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.2.2 🤖 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 e135b4a to 4d52fa9 Compare January 13, 2026 10:46
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.2.3 🤖 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 4d52fa9 to 241ae95 Compare January 14, 2026 18:09
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.2.4 🤖 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 241ae95 to 07010d2 Compare January 22, 2026 21:32
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.2.5 🤖 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 07010d2 to e62c9d3 Compare February 2, 2026 09:41
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.2.6 🤖 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 e62c9d3 to 722dbdc Compare February 18, 2026 14:48
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.3.0 🤖 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 722dbdc to 7610378 Compare February 22, 2026 16:40
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.3.1 🤖 Update dependency argoproj/argo-cd to v3.3.2 Feb 22, 2026
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 7610378 to b0cee43 Compare March 9, 2026 18:04
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.3.2 🤖 Update dependency argoproj/argo-cd to v3.3.3 Mar 9, 2026
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from b0cee43 to 906b894 Compare March 16, 2026 14:44
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.3.3 🤖 Update dependency argoproj/argo-cd to v3.3.4 Mar 16, 2026
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 906b894 to 67bcf51 Compare March 25, 2026 16:29
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.3.4 🤖 Update dependency argoproj/argo-cd to v3.3.5 Mar 25, 2026
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 67bcf51 to 1e03ef7 Compare March 27, 2026 14:14
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.3.5 🤖 Update dependency argoproj/argo-cd to v3.3.6 Mar 27, 2026
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 1e03ef7 to 10eb1aa Compare April 16, 2026 15:13
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.3.6 🤖 Update dependency argoproj/argo-cd to v3.3.7 Apr 16, 2026
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from 10eb1aa to c45785f Compare April 21, 2026 19:17
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.3.7 🤖 Update dependency argoproj/argo-cd to v3.3.8 Apr 21, 2026
@renovate renovate Bot force-pushed the renovate/argoproj-argo-cd-3.x branch from c45785f to e2f4fda Compare April 30, 2026 20:06
@renovate renovate Bot changed the title 🤖 Update dependency argoproj/argo-cd to v3.3.8 🤖 Update dependency argoproj/argo-cd to v3.3.9 Apr 30, 2026
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