Dependency Dashboard

[renovate[bot]]

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• [ ] chore(deps): update all non-major dependencies (gitea, k3s-io/k3s, weaveworks/eksctl)

Detected dependencies

cargo

src/injector/Cargo.toml

dockerfile

Dockerfile

github-actions

.github/actions/golang/action.yaml

.github/actions/install-tools/action.yaml

.github/actions/save-logs/action.yaml

.github/actions/slack/action.yaml

.github/workflows/build-rust-injector.yml

.github/workflows/commitlint.yml

.github/workflows/dependency-review.yml

.github/workflows/dummy-dco.yaml

.github/workflows/nightly-ecr.yml

.github/workflows/nightly-eks.yml

.github/workflows/publish-application-packages.yml

.github/workflows/release.yml

.github/workflows/scan-codeql.yml

.github/workflows/scan-docs-and-schema.yml

.github/workflows/scan-lint.yml

.github/workflows/scorecard.yaml

.github/workflows/test-bigbang.yml

.github/workflows/test-e2e-shim.yml

.github/workflows/test-e2e.yml

.github/workflows/test-external.yml

.github/workflows/test-site.yml

.github/workflows/test-unit.yml

.github/workflows/test-upgrade.yml

.github/workflows/test-windows.yml

gomod

go.mod

src/api/go.mod

helm-values

packages/zarf-registry/chart/values.yaml

- `registry 2.8.3`

npm

site/package.json

regex

packages/gitea/zarf.yaml

- `gitea 10.1.1`

packages/distros/eks/zarf.yaml

- `weaveworks/eksctl v0.170.0` - `weaveworks/eksctl v0.170.0` - `weaveworks/eksctl v0.170.0`

packages/distros/k3s/zarf.yaml

- `k3s-io/k3s v1.28.4+k3s2` - `k3s-io/k3s v1.28.4+k3s2` - `k3s-io/k3s v1.28.4+k3s2` - `k3s-io/k3s v1.28.4+k3s2`

---

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

[JasonvanBrackel]

@jeff-mccoy I think this is a non-issue given you closed it once. Not sure why renovate reopened it. Can you take a look?

[RothAndrew]

Renovate uses it as a persistent dashboard where it will show the queue of changes to be made and a list of changes that have been "snoozed" with a way to "unsnooze" them. If you want to disable it it needs to be done in the renovate config file. Otherwise Renovate will continue to reopen it.

My recommendation would be to continue using it. I find it to be quite helpful over in the DI2-ME repo.

[JasonvanBrackel]

I'll put this on the backlog then thanks @RothAndrew