alexlebens/infrastructure
1
0
Fork 0
Code Issues 1 Pull Requests 5 Actions Activity

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

Merged
renovate-bot merged 1 commits from renovate/unified-argoprojargo-cd into main 2026-02-23 14:03:00 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2026-02-23 14:02:44 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
argoproj/argo-cd patch v3.3.1 → v3.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: https://github.com/argoproj/argo-cd/compare/v3.3.1...v3.3.2

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [argoproj/argo-cd](https://github.com/argoproj/argo-cd) | patch | `v3.3.1` → `v3.3.2` | --- ### Release Notes <details> <summary>argoproj/argo-cd (argoproj/argo-cd)</summary> ### [`v3.3.2`](https://github.com/argoproj/argo-cd/releases/tag/v3.3.2) [Compare Source](https://github.com/argoproj/argo-cd/compare/v3.3.1...v3.3.2) > \[!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: [#&#8203;26279](https://github.com/argoproj/argo-cd/issues/26279) > > For users who have previously upgraded to Argo CD `3.3.0`or `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: ```shell 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: ```shell 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](https://argo-cd.readthedocs.io/en/stable/operator-manual/signed-release-assets) 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](https://blog.argoproj.io/argo-cd-v3-0-release-candidate-a0b933f4e58f) #### Upgrading If upgrading from a different minor version, be sure to read the [upgrading](https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/) documentation. #### Changelog ##### Bug fixes - [`67c2319`](https://github.com/argoproj/argo-cd/commit/67c23193c4dc23defb4cad555ba975cf501ba1b0): fix: use csapgrade to patch managedFields for client-side apply migration (cherry-pick [#&#8203;26289](https://github.com/argoproj/argo-cd/issues/26289) for 3.3) ([#&#8203;26516](https://github.com/argoproj/argo-cd/issues/26516)) ([@&#8203;argo-cd-cherry-pick-bot](https://github.com/argo-cd-cherry-pick-bot)\[bot]) ##### Documentation - [`1bf62ae`](https://github.com/argoproj/argo-cd/commit/1bf62aea1991a772769b110d8a10e8d56a3c1eb2): docs: instruct to enable ClientSideApplyMigration in 3.3.2 (cherry-pick [#&#8203;26547](https://github.com/argoproj/argo-cd/issues/26547) for 3.3) ([#&#8203;26549](https://github.com/argoproj/argo-cd/issues/26549)) ([@&#8203;argo-cd-cherry-pick-bot](https://github.com/argo-cd-cherry-pick-bot)\[bot]) **Full Changelog**: <https://github.com/argoproj/argo-cd/compare/v3.3.1...v3.3.2> <a href="https://argoproj.github.io/cd/"><img src="https://raw.githubusercontent.com/argoproj/argo-site/master/content/pages/cd/gitops-cd.png" width="25%" ></a> </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNS44IiwidXBkYXRlZEluVmVyIjoiNDMuMjUuOCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYXV0b21lcmdlIiwiaW1hZ2UiXX0=-->
renovate-bot added the automergeimage labels 2026-02-23 14:02:44 +00:00
renovate-bot added 1 commit 2026-02-23 14:02:46 +00:00
chore(deps): update dependency argoproj/argo-cd to v3.3.2
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
render-manifests-merge / render-manifests-merge (pull_request) Has been skipped
Details
lint-test-helm / lint-helm (pull_request) Successful in 45s
Details
render-manifests-automerge / render-manifests-automerge (pull_request) Successful in 1m4s
Details
dbaeac3ec5
renovate-bot scheduled this pull request to auto merge when all checks succeed 2026-02-23 14:02:50 +00:00
renovate-bot merged commit 3c93618690 into main 2026-02-23 14:03:00 +00:00
renovate-bot deleted branch renovate/unified-argoprojargo-cd 2026-02-23 14:03:08 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Renovate
Issue generated by Renovate.
 automerge
This PR will be automerged by Renovate.
 chart
Chart update generated by Renovate.
 image
Image update generated by Renovate.
 stale
PR or Issue that has not been updated recently.
No Label automerge image
Milestone
No items
No Milestone
Assignees
Clear assignees
gitea-bot renovate-bot alexlebens
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alexlebens/infrastructure#4175
Delete Branch "renovate/unified-argoprojargo-cd"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?