Argo
v3.1.15CI/CD & App DeliveryPatch release with two targeted bug fixes: a revert of a problematic refresh prevention change and a core mode sync failure when server.secretkey is absent.
breakingRevert of refresh-prevention fix may re-expose original behavior
The cherry-picked fix for preventing automatic refreshes from informer resyncs and status updates was reverted because it caused problems in 3.1. If you upgraded to 3.1.x specifically expecting that behavior to be fixed, it's gone again. Watch the upstream issue for a corrected implementation before relying on it. No action needed otherwise, but be aware of potential extra refresh churn in large clusters.
enhancementUpgrade immediately if running Argo CD in core mode without server.secretkey
A bug caused the application controller to fail syncing entirely when running in core mode and the server.secretkey was absent from the cluster secret. If your core-mode installations have ever had intermittent sync failures that were hard to diagnose, this is likely the culprit. Upgrade to 3.1.15 and verify syncs resume normally after rollout.
Key changes (3)
- Reverted the automatic refresh prevention fix (#25290) that was cherry-picked into 3.1 — the fix itself caused regressions
- Fixed app controller core mode failing to sync when server.secretkey is missing from the cluster secret
- All container images remain cosign-signed with SLSA Level 3 provenance