Configure Renovate

[umts-renovate]

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

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 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 and select the Retry/Rebase checkbox below. Renovate will update the Pull Request description the next time it runs.

---

Detected Package Files

• Gemfile (bundler)
• Dockerfile (dockerfile)
• .github/workflows/integrate.yml (github-actions)
• renovate.json (renovate-config)
• .ruby-version (ruby-version)

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.

---

What to Expect

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

Pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/pin-dependencies
• Merge into: main
• Upgrade docker/dockerfile to sha256:ecfaec9ed6d810b56388c508f4121597bfbba70d41a6dfeee4d8cad5f295fc32
• Upgrade ruby to sha256:ff7780d9fc05a54690c722ee0621bae2aa818331be88ebbeb0f5e7bd7cdb7f37

Update dependency ruby to v3.4.10

• Schedule: ["at any time"]
• Branch name: renovate/ruby-3.x
• Merge into: main
• Upgrade ruby to 3.4.10
• Upgrade ruby to sha256:66ce991f12c58f5038c9f7c34df36d624d10c84500b748a7036c621c43cf154e

Update dependency rubocop-rails to v2.37.0

• Schedule: ["at any time"]
• Branch name: renovate/rubocop-rails-2.x-lockfile
• Merge into: main
• Upgrade rubocop-rails to 2.37.0

Update dependency ruby to v4

• Schedule: ["at any time"]
• Branch name: renovate/ruby-4.x
• Merge into: main
• Upgrade ruby to 4.0.6
• Upgrade ruby to sha256:607bf92fa7ecebb4a0c6654b62cb44c48d94b36b6f5a754611ddbbe3dc5b6135

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

---

❓ 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.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate CLI.