[onboarding-archived 2026-06-29] Configure Renovate

[public-glueops-renovatebot]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

Detected Package Files

• k3d-config.yaml (helm-values)
• k3d-config.yaml (kubernetes)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs
• Pin Docker digests.
• Pin github-action digests.
• Pin dependency versions for development dependencies.

---

What to Expect

With your current configuration, Renovate will create 3 Pull Requests:

chore(patch): update dockerhub.repo.gpkg.io/rancher/k3s to v1.34.9 #patch

• Schedule: ["at any time"]
• Branch name: renovate/dockerhub.repo.gpkg.io-rancher-k3s-1.34.x
• Merge into: main
• Upgrade dockerhub.repo.gpkg.io/rancher/k3s to sha256:9c162556657a38e394d1f944081388ae7c0b85ec29134c509583083e287f804e

feat: update dockerhub.repo.gpkg.io/rancher/k3s to v1.35.6 #minor

• Schedule: ["at any time"]
• Branch name: renovate/dockerhub.repo.gpkg.io-rancher-k3s-1.35.x
• Merge into: main
• Upgrade dockerhub.repo.gpkg.io/rancher/k3s to sha256:9d6b9c15e8031c1aea7dd7f0cdc019f5e74a23c53b9eada564b7a8dc94efc14c

feat: update dockerhub.repo.gpkg.io/rancher/k3s to v1.36.2 #minor

• Schedule: ["at any time"]
• Branch name: renovate/dockerhub.repo.gpkg.io-rancher-k3s-1.36.x
• Merge into: main
• Upgrade dockerhub.repo.gpkg.io/rancher/k3s to sha256:6a47cea22c4b834d4ba72c89d291696b79ebe406251f90b446e4dff03513dd87

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR has been generated by Mend Renovate.