Skip to content

chore(deps): update quay.io/argoproj/argocd docker tag to v3.5.1 - #429

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/quay.io-argoproj-argocd-3.x
Open

chore(deps): update quay.io/argoproj/argocd docker tag to v3.5.1#429
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/quay.io-argoproj-argocd-3.x

Conversation

@renovate

@renovate renovate Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
quay.io/argoproj/argocd minor v3.4.5v3.5.1

⚠️ Manual apply required. ArgoCD does not manage its own bootstrap manifest, so this PR cannot be auto-applied by the cluster.

After merging, run:

kubectl --context yornik-sharkshere apply --server-side --force-conflicts \

-k bootstrap/argocd/

--server-side is required because ArgoCD's applicationsets.argoproj.io CRD has an OpenAPI schema larger than the 256 KiB annotation limit used by client-side kubectl apply. --force-conflicts lets server-side apply take ownership of fields previously managed by older client-side applies.

Then verify the rollout and that all Applications stay healthy:

kubectl --context yornik-sharkshere -n argocd rollout status \

deploy/argocd-server deploy/argocd-repo-server \

statefulset/argocd-application-controller

kubectl --context yornik-sharkshere -n argocd get applications

Rollback (if needed): revert the commit on main, run the same kubectl apply --server-side --force-conflicts -k bootstrap/argocd/ again to restore the previous version.


Release Notes

argoproj/argo-cd (quay.io/argoproj/argocd)

v3.5.1

Compare Source

v3.5.0

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.5.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.5.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

Note

PR body was truncated to here.

@renovate
renovate Bot force-pushed the renovate/quay.io-argoproj-argocd-3.x branch 7 times, most recently from 1f3de75 to b104f99 Compare August 11, 2026 20:52
@renovate
renovate Bot force-pushed the renovate/quay.io-argoproj-argocd-3.x branch from b104f99 to 0a275c9 Compare August 12, 2026 13:35
@renovate renovate Bot changed the title chore(deps): update quay.io/argoproj/argocd docker tag to v3.5.0 chore(deps): update quay.io/argoproj/argocd docker tag to v3.5.1 Aug 12, 2026
@renovate
renovate Bot force-pushed the renovate/quay.io-argoproj-argocd-3.x branch from 0a275c9 to b0930b5 Compare August 17, 2026 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants