build(deps): Bump github.com/argoproj/argo-cd/v2 from 2.9.10 to 2.9.12

[dependabot]

Bumps github.com/argoproj/argo-cd/v2 from 2.9.10 to 2.9.12.

Release notes

Sourced from github.com/argoproj/argo-cd/v2's releases.

v2.9.12

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.9.12/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.9.12/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.

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Full Changelog: argoproj/argo-cd@v2.9.11...v2.9.12

v2.9.11

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.9.11/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.9.11/manifests/ha/install.yaml

Release Signatures and Provenance

... (truncated)

Commits

• d6cb4e9 fix: docker build fails due to "The repository 'http://deb.debian.org/debian ...
• 710ee9a Bump version to 2.9.12 (#17832)
• e0ff56d Merge pull request from GHSA-2gvw-w6fj-7m3c
• 91bb155 Bump version to 2.9.11 (#17742)
• 7ff0ccc fix: fix calculating patch for respect ignore diff feature (#17693)
• b17323b chore(deps): bump webpack-dev-middleware from 5.3.1 to 5.3.4 in /ui (#17598) ...
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[the-technat]

LGTM

@oboukili what kind of strategy do you have for bumping argo-deps in the provider? Currently the README says n-2 but n doesn't seem to be specified somewhere (and would also not be the latest argo-cd version currently).

[onematchfox]

@oboukili what kind of strategy do you have for bumping argo-deps in the provider?

We generally only bump deps when needed - which is when someone wants to make use of a feature introduced in a newer version and/or if we bump test versions and something fails.

Currently the README says n-2 but n doesn't seem to be specified somewhere (and would also not be the latest argo-cd version currently).

Read a little further 😄:

This provider is compatible with at least the last 2 minor releases of ArgoCD (e.g, ranging from 1.(n).m, to 1.(n-1).0, where n is the latest available minor version).

As such, given that 2.10 is the latest minor version, the compatability promise of the provider is that it will work with version 2.8, 2.9 and 2.10. Note however, that there isn't a strong coupling between the version of the module this provider imports and the versions of ArgoCD that it can make use of. The provider can still import v2.9 of the module to make calls to a v2.10 API server.