Argo CD v1.8.7stable Released Mar 03, 2021
Impact Score: 5/10

Argo CD v1.8.7 โ€” Release Notes & Engineering Impact

Source available โ€” automated, not human-reviewed

Component: argocd ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-01.

Compatibility not verified โ€” check source notes
๐Ÿ“„ .MD
โšก Executive Summary (TL;DR)

Argo CD v1.8.7. Source highlight: kubectl create namespace argocd

Who Does This Impact? (Role-Based Analysis)

๐Ÿ’ป Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

๐Ÿ“Š Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

โš™๏ธ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

๐Ÿ”ง Bug Fixes & Patches (3)

  • fix: redact sensitive data in logs (#5662)
  • fix: Properly escape HTML for error message from CLI SSO (#5563)
  • fix: Empty resource whitelist allowed all resources (#5540) (#5551)
๐Ÿ“„ View Raw Release Notes (Original Developer Log)
## Quick Start ### Non-HA: ```bash kubectl create namespace argocd kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v1.8.7/manifests/install.yaml ``` #### HA: ```bash kubectl create namespace argocd kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v1.8.7/manifests/ha/install.yaml ``` ## Important note This release fixed a regression regarding which cluster resources are permitted on the AppProject level. Previous to this fix, after #3960 has been merged, all cluster resources were allowed on project level when neither of the allow or deny lists was defined. However, the correct behavior is to block all resources in this case. If you have Projects with empty allow and deny lists, but want the associated applications be able to sync cluster resources, you will have to adapt your cluster resources allow lists to explicitly allow the resources. #### Bug Fixes - fix: redact sensitive data in logs (#5662) - fix: Properly escape HTML for error message from CLI SSO (#5563) - fix: Empty resource whitelist allowed all resources (#5540) (#5551)