Configure Renovate #9

Merged
florian merged 1 commit from renovate/configure into main 2026-06-14 02:49:33 +02:00
Collaborator

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. Renovate will update the Pull Request description the next time it runs.


Detected Package Files

  • .github/workflows/ci.yml (github-actions)
  • package.json (npm)

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
  • Enable Renovate Dependency Dashboard creation.

What to Expect

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

Update dependency @​types/node to v22.19.21
  • Schedule: ["at any time"]
  • Branch name: renovate/node-22.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 22.19.21
Update dependency @​vitejs/plugin-react to v6.0.2
  • Schedule: ["at any time"]
  • Branch name: renovate/vitejs-plugin-react-6.x-lockfile
  • Merge into: main
  • Upgrade @vitejs/plugin-react to 6.0.2
Update nextjs monorepo to v15.5.19
  • Schedule: ["at any time"]
  • Branch name: renovate/nextjs-monorepo
  • Merge into: main
  • Upgrade next to 15.5.19
Update react monorepo
  • Schedule: ["at any time"]
  • Branch name: renovate/react-monorepo
  • Merge into: main
  • Upgrade @types/react to 19.2.17
  • Upgrade react to 19.2.7
  • Upgrade react-dom to 19.2.7
Update vitest monorepo to v4.1.8
  • Schedule: ["at any time"]
  • Branch name: renovate/vitest-monorepo
  • Merge into: main
  • Upgrade vitest to 4.1.8
Update dependency mermaid to v11.15.0
  • Schedule: ["at any time"]
  • Branch name: renovate/mermaid-11.x-lockfile
  • Merge into: main
  • Upgrade mermaid to 11.15.0
Update dependency yaml to v2.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/yaml-2.x-lockfile
  • Merge into: main
  • Upgrade yaml to 2.9.0
Update actions/checkout action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to v6
Update actions/setup-node action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to v6
Update dependency node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24
  • Upgrade @types/node to ^24.0.0
Update dependency typescript to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-6.x
  • Merge into: main
  • Upgrade typescript to ^6.0.0
Update nextjs monorepo to v16
  • Schedule: ["at any time"]
  • Branch name: renovate/major-nextjs-monorepo
  • Merge into: main
  • Upgrade next to ^16.0.0

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


This PR has been generated by Mend Renovate.

Welcome to [Renovate](https://github.com/renovatebot/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](https://docs.renovatebot.com/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 * `.github/workflows/ci.yml` (github-actions) * `package.json` (npm) ### 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 - Enable Renovate Dependency Dashboard creation. --- ### What to Expect With your current configuration, Renovate will create 12 Pull Requests: <details> <summary>Update dependency @&#8203;types/node to v22.19.21</summary> - Schedule: ["at any time"] - Branch name: `renovate/node-22.x-lockfile` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `22.19.21` </details> <details> <summary>Update dependency @&#8203;vitejs/plugin-react to v6.0.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/vitejs-plugin-react-6.x-lockfile` - Merge into: `main` - Upgrade [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react) to `6.0.2` </details> <details> <summary>Update nextjs monorepo to v15.5.19</summary> - Schedule: ["at any time"] - Branch name: `renovate/nextjs-monorepo` - Merge into: `main` - Upgrade [next](https://github.com/vercel/next.js) to `15.5.19` </details> <details> <summary>Update react monorepo</summary> - Schedule: ["at any time"] - Branch name: `renovate/react-monorepo` - Merge into: `main` - Upgrade [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped) to `19.2.17` - Upgrade [react](https://github.com/facebook/react) to `19.2.7` - Upgrade [react-dom](https://github.com/facebook/react) to `19.2.7` </details> <details> <summary>Update vitest monorepo to v4.1.8</summary> - Schedule: ["at any time"] - Branch name: `renovate/vitest-monorepo` - Merge into: `main` - Upgrade [vitest](https://github.com/vitest-dev/vitest) to `4.1.8` </details> <details> <summary>Update dependency mermaid to v11.15.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/mermaid-11.x-lockfile` - Merge into: `main` - Upgrade [mermaid](https://github.com/mermaid-js/mermaid) to `11.15.0` </details> <details> <summary>Update dependency yaml to v2.9.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/yaml-2.x-lockfile` - Merge into: `main` - Upgrade [yaml](https://github.com/eemeli/yaml) to `2.9.0` </details> <details> <summary>Update actions/checkout action to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-6.x` - Merge into: `main` - Upgrade [actions/checkout](https://github.com/actions/checkout) to `v6` </details> <details> <summary>Update actions/setup-node action to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-setup-node-6.x` - Merge into: `main` - Upgrade [actions/setup-node](https://github.com/actions/setup-node) to `v6` </details> <details> <summary>Update dependency node to v24</summary> - Schedule: ["at any time"] - Branch name: `renovate/node-24.x` - Merge into: `main` - Upgrade [node](https://github.com/actions/node-versions) to `24` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `^24.0.0` </details> <details> <summary>Update dependency typescript to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/typescript-6.x` - Merge into: `main` - Upgrade [typescript](https://github.com/microsoft/TypeScript) to `^6.0.0` </details> <details> <summary>Update nextjs monorepo to v16</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-nextjs-monorepo` - Merge into: `main` - Upgrade [next](https://github.com/vercel/next.js) to `^16.0.0` </details> 🚸 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`](https://docs.renovatebot.com/configuration-options/#prhourlylimit) for details. --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-config-hash:f45a09b7dfde7a562e5fe1fdc33ab1653a6b971df092f81a37906415a163370f-->
Add renovate.json
All checks were successful
CI / build (push) Successful in 1m23s
CI / build (pull_request) Successful in 1m12s
92174658c8
Sign in to join this conversation.
No description provided.