We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 19 since February 2026, each linked to its source.
argocdWhen a role needs to toggle an Application's auto-sync without broad update access, grant the dedicated action permission and run `toggle-auto-sync` on the Application. Disabling saves the documented auto-sync settings, while enabling restores saved settings when present.
p, role:dev, applications, action/argoproj.io/Application/toggle-auto-sync, */*, allowWhen the ApplicationSet controller must reach GitHub, GitLab, Gitea, or Bitbucket Server APIs through a proxy, set `--scm-proxy-url` and optionally `--scm-no-proxy` (or their documented environment variables). These settings route outbound SCM API requests; use `--proxy-url` for Kubernetes API traffic.
argocd-applicationset-controller \
--scm-proxy-url=http://<proxy-host>:<port> \
--scm-no-proxy=<host-or-CIDR>[,<host-or-CIDR>...]When configuring an ApplicationSet SCM generator for GitHub or Gitea, set `excludeArchivedRepos: true` to exclude archived repositories; for GitLab, set `includeArchivedRepos: true` to include them. Both fields default to false.
apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
name: <appset-name>
spec:
generators:
- scmProvider:
github:
organization: <github-organization>
excludeArchivedRepos: trueWhen resolving a Git semver target within a tag path, set `tagPrefix` with `targetRevision`. Argo CD filters tags by that prefix, strips it for constraint evaluation, then restores it on the resolved version; semver constraints match tags, not branches.
argocd app set <APPNAME> --revision '1.0.*' --tag-prefix 'component-b/'When reviewing a Karpenter v1 `karpenter.sh/NodeClaim` in Argo CD, use the bundled v3.5.0 health check: it reports Progressing while status is absent or Launched, Registered, or Initialized is reached; Healthy for `Ready=True`, Degraded for `Ready=False`, and Suspended for `Disrupting=True`.
kubectl get nodeclaims.karpenter.sh <nodeclaim-name> -o yamlWhen a role needs to toggle auto-sync from the application details page without broad application update permission, grant the `toggle-auto-sync` action and application `get` access for the target application.
p, role:oncall, applications, action/argoproj.io/Application/toggle-auto-sync, */*, allow
p, role:oncall, applications, get, */*, allowWhen GHCR artifacts are published, configure a GitHub repository webhook to POST package events to `https://<argocd-server>/api/webhook` with content type `application/json` and Packages enabled. Set the same webhook secret in GitHub and `argocd-secret` as `webhook.github.secret`; only published container package events trigger refreshes for matching Applications.
GitHub repository → Settings → Webhooks → Add webhook; Payload URL: `https://<argocd-server>/api/webhook`; Content type: `application/json`; Secret: `<your-webhook-secret>`; Events: select individual events and enable Packages.When an ApplicationSet manages many Applications and reconciliation is slow, start the v3.5.0 ApplicationSet controller with `--concurrent-application-updates` set to the desired concurrency.
argocd-applicationset-controller --concurrent-application-updates <N>When creating or generating an ApplicationSet, use `-N` / `--appset-namespace` only if its manifest omits `metadata.namespace`; the manifest namespace takes precedence. For get or delete, use the flag to select a namespace, unless the name is qualified as `namespace/name`, which takes precedence.
argocd appset create --appset-namespace=<APPSET_NAMESPACE> <filename-or-URL> [<filename-or-URL>...]When managing an Argo CD project’s Git source integrity policies, use the `argocd proj source-integrity git policies` subcommands to list, add, update, or delete policies. The v3.5 command reference gives full invocations only for listing and deleting; it leaves add and update arguments unspecified.
argocd proj source-integrity git policies list <PROJECT>