Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/adobe/rules_gitops).

## Config Migration Needed

- [ ] Select this checkbox to let Renovate create an automated Config Migration PR.

## Rate-Limited

The following updates are currently rate-limited. To force their creation now, click on a checkbox below.

- [ ] Update module google.golang.org/protobuf to v1.36.12
- [ ] Update dependency rules_go to v0.63.0
- [ ] Update kubernetes monorepo to v0.37.0 (`k8s.io/api`, `k8s.io/apimachinery`, `k8s.io/client-go`)
- [ ] Update module github.com/xanzy/go-gitlab to v0.115.0
- [ ] Update module sigs.k8s.io/kind to v0.33.0
- [ ] Update actions/cache action to v6
- [ ] Update actions/checkout action to v7
- [ ] Update amannn/action-semantic-pull-request action to v6
- [ ] Update module github.com/google/go-github/v32 to v91
- [ ] 🔐 **Create all rate-limited PRs at once** 🔐

## Open

The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.

- [ ] [Update module golang.org/x/oauth2 to v0.27.0 [SECURITY]](../pull/186)
- [ ] [Update alpine:3.23 Docker digest to fd791d7](../pull/196)
- [ ] [Update dependency rules_img to v0.3.21](../pull/197)
- [ ] [Update alpine Docker tag to v3.24](../pull/205)
- [ ] [Update alpine_linux_amd64 Docker tag to v3.24](../pull/198)
- [ ] [Update bazel-contrib/.github action to v7.7.0](../pull/199)
- [ ] [Update bazel-contrib/publish-to-bcr action to v1.5.0](../pull/200)
- [ ] [Update dependency bazel to v7.7.1](../pull/201)
- [ ] [Update dependency io_bazel_rules_go to v0.63.0](../pull/203)
- [ ] [Update dependency platforms to v1.1.0](../pull/206)
- [ ] [Update dependency bazel to v9](../pull/194)
- [ ] **Click on this checkbox to rebase all open PRs at once**

## Detected Dependencies

bazel (1)

examples/legacy_docker/WORKSPACE (3)

- `io_bazel_rules_go v0.51.0` → [Updates: `v0.63.0`]
- `io_bazel_rules_docker v0.26.0`
- `alpine_linux_amd64 3.8@sha256:954b378c375d852eb3c63ab88978f640b4348b01c1b3456a024a81536dafbbf4` → [Updates: `3.24`]

bazel-module (3)

examples/helloworld/MODULE.bazel (4)

- `platforms 1.0.0` → [Updates: `1.1.0`]
- `rules_go 0.52.0` → [Updates: `0.63.0`]
- `rules_img 0.3.3` → [Updates: `0.3.21`]
- `alpine 3.23@sha256:51183f2cfa6320055da30872f211093f9ff1d3cf06f39a0bdb212314c5dc7375` → [Updates: `3.24`, `3.23`]

examples/legacy_docker/MODULE.bazel

MODULE.bazel

bazelisk (3)

.bazelversion (1)

- `bazel 7.6.0` → [Updates: `7.7.1`, `9.2.0`]

examples/helloworld/.bazelversion (1)

- `bazel 7.6.0` → [Updates: `7.7.1`, `9.2.0`]

examples/legacy_docker/.bazelversion (1)

- `bazel 7.6.0` → [Updates: `7.7.1`, `9.2.0`]

github-actions (4)

.github/workflows/ci.yaml (3)

- `actions/checkout v3` → [Updates: `v7`]
- `actions/cache v4` → [Updates: `v6`]
- `ubuntu 24.04`

.github/workflows/conventional-commits.yaml (1)

- `amannn/action-semantic-pull-request v5` → [Updates: `v6`]

.github/workflows/publish.yaml (1)

- `bazel-contrib/publish-to-bcr v1.0.0` → [Updates: `v1.5.0`]

.github/workflows/release.yml (1)

- `bazel-contrib/.github v7.2.2` → [Updates: `v7.7.0`]

gomod (1)

go.mod (11)

- `go 1.24.12`
- `github.com/ghodss/yaml v1.0.0`
- `github.com/google/go-cmp v0.7.0`
- `github.com/google/go-github/v32 v32.1.0` → [Updates: `v91.0.0`]
- `github.com/xanzy/go-gitlab v0.80.2` → [Updates: `v0.115.0`]
- `golang.org/x/oauth2 v0.5.0` → [Updates: `v0.27.0`]
- `google.golang.org/protobuf v1.36.11` → [Updates: `v1.36.12`]
- `k8s.io/api v0.26.1` → [Updates: `v0.37.0`]
- `k8s.io/apimachinery v0.26.1` → [Updates: `v0.37.0`]
- `k8s.io/client-go v0.26.1` → [Updates: `v0.37.0`]
- `sigs.k8s.io/kind v0.31.0` → [Updates: `v0.33.0`]

---

- [ ] Check this box to trigger a request for Renovate to run again on this repository

Il s’agit d’un tableau de bord généré par Renovate plutôt que d’une tâche de code ciblée. Commencez par les entrées limitées par le débit et examinez les pull requests associés, en particulier #186 et #194–#206. Le travail est considéré comme terminé lorsque la mise à jour de dépendance sélectionnée a été examinée, passe les vérifications du dépôt et est fusionnée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.