chore: Configure Renovate

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

---

Detected Package Files

• .github/workflows/cache-clear.yml (github-actions)
• .github/workflows/codeql.yml (github-actions)
• .github/workflows/dependency-review.yml (github-actions)
• .github/workflows/greetings.yml (github-actions)
• .github/workflows/introspect.yml (github-actions)
• .github/workflows/lint.yml (github-actions)
• .github/workflows/scorecards.yml (github-actions)
• .github/workflows/semantic-pull-request.yml (github-actions)
• .github/workflows/semantic-release.yml (github-actions)
• .github/workflows/stale-issues.yml (github-actions)
• .github/workflows/test.yml (github-actions)
• package.json (npm)
• .nvmrc (nvm)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• Show all Merge Confidence badges for pull requests.
• 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 directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Evaluate schedules according to timezone Europe/Berlin.
• Weekly schedule on early Monday mornings.
• Run Renovate on following schedule: before 4am on Monday

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

---

What to Expect

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

chore(deps): update dependency renovate to ^37.33.4

• Schedule: ["before 4am on Monday"]
• Branch name: renovate/patch-renovate
• Merge into: main
• Upgrade renovate to ^37.33.4

chore(deps): update pnpm to v8.10.2

• Schedule: ["before 4am on Monday"]
• Branch name: renovate/patch-patch-updates
• Merge into: main
• Upgrade pnpm to 8.10.2

chore(deps): lock file maintenance

• Schedule: ["before 4am on monday"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions

🚸 Branch 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.

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

Great! Thank you for taking the time to create your first pull request! Please review the guidelines

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.