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/ci.yml (github-actions)
• .github/workflows/pr-pkg-new.yml (github-actions)
• .stackblitz/package.json (npm)
• docs/package.json (npm)
• package.json (npm)
• playground/package.json (npm)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• 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 (except for nuget) 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.

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

---

What to Expect

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

chore(deps): update dependency nuxt to v3.12.4 [security]

• Branch name: renovate/npm-nuxt-vulnerability
• Merge into: main
• Upgrade nuxt to 3.12.4

chore(deps): update dependency vitest to v1.6.1 [security]

• Branch name: renovate/npm-vitest-vulnerability
• Merge into: main
• Upgrade vitest to 1.6.1

chore(deps): update dependency @iconify-json/ph to v1.2.2

• Schedule: ["at any time"]
• Branch name: renovate/iconify-json-ph-1.x-lockfile
• Merge into: main
• Upgrade @iconify-json/ph to 1.2.2

chore(deps): update dependency @iconify-json/simple-icons to v1.2.25

• Schedule: ["at any time"]
• Branch name: renovate/iconify-json-simple-icons-1.x-lockfile
• Merge into: main
• Upgrade @iconify-json/simple-icons to 1.2.25

chore(deps): update dependency @​nuxt/module-builder to v0.8.4

• Schedule: ["at any time"]
• Branch name: renovate/nuxt-module-builder-0.x-lockfile
• Merge into: main
• Upgrade @nuxt/module-builder to 0.8.4

chore(deps): update dependency @​types/node to v18.19.76

• Schedule: ["at any time"]
• Branch name: renovate/node-18.x-lockfile
• Merge into: main
• Upgrade @types/node to 18.19.76

chore(deps): update dependency eslint to v8.57.1

• Schedule: ["at any time"]
• Branch name: renovate/eslint-monorepo
• Merge into: main
• Upgrade eslint to 8.57.1

chore(deps): update yarn to v1.22.22

• Schedule: ["at any time"]
• Branch name: renovate/yarn-1.x
• Merge into: main
• Upgrade yarn to 1.22.22

chore(deps): update dependency @​nuxt/devtools to v1.7.0

• Schedule: ["at any time"]
• Branch name: renovate/nuxt-devtools-1.x-lockfile
• Merge into: main
• Upgrade @nuxt/devtools to 1.7.0

chore(deps): update dependency @​nuxt/eslint-config to ^0.7.0

• Schedule: ["at any time"]
• Branch name: renovate/nuxt-eslint-config-0.x
• Merge into: main
• Upgrade @nuxt/eslint-config to ^0.7.0

chore(deps): update dependency @​nuxt/test-utils to v3.17.0

• Schedule: ["at any time"]
• Branch name: renovate/nuxt-test-utils-3.x-lockfile
• Merge into: main
• Upgrade @nuxt/test-utils to 3.17.0

chore(deps): update dependency @​nuxt/ui-pro to v1.7.0

• Schedule: ["at any time"]
• Branch name: renovate/nuxt-ui-pro-1.x-lockfile
• Merge into: main
• Upgrade @nuxt/ui-pro to 1.7.0

chore(deps): update dependency @​vueuse/nuxt to v11.3.0

• Schedule: ["at any time"]
• Branch name: renovate/vueuse-monorepo
• Merge into: main
• Upgrade @vueuse/nuxt to 11.3.0

chore(deps): update dependency typescript to v5.7.3

• Schedule: ["at any time"]
• Branch name: renovate/typescript-5.x-lockfile
• Merge into: main
• Upgrade typescript to 5.7.3

fix(deps): update nuxtjs monorepo to v3.15.4

• Schedule: ["at any time"]
• Branch name: renovate/nuxtjs-monorepo
• Merge into: main
• Upgrade @nuxt/kit to 3.15.4
• Upgrade @nuxt/schema to 3.15.4
• Upgrade nuxt to 3.15.4

chore(deps): update actions/cache action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-cache-4.x
• Merge into: main
• Upgrade actions/cache to v4

chore(deps): update actions/setup-node action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-node-4.x
• Merge into: main
• Upgrade actions/setup-node to v4

chore(deps): update dependency @​nuxt/content to v3

• Schedule: ["at any time"]
• Branch name: renovate/nuxt-content-3.x
• Merge into: main
• Upgrade @nuxt/content to ^3.0.0

chore(deps): update dependency @​nuxt/devtools to v2

• Schedule: ["at any time"]
• Branch name: renovate/nuxt-devtools-2.x
• Merge into: main
• Upgrade @nuxt/devtools to ^2.0.0

chore(deps): update dependency @​nuxt/eslint-config to v1

• Schedule: ["at any time"]
• Branch name: renovate/nuxt-eslint-config-1.x
• Merge into: main
• Upgrade @nuxt/eslint-config to ^1.0.0

chore(deps): update dependency @​types/node to v22

• Schedule: ["at any time"]
• Branch name: renovate/node-22.x
• Merge into: main
• Upgrade @types/node to ^22.0.0

chore(deps): update dependency @​vueuse/nuxt to v12

• Schedule: ["at any time"]
• Branch name: renovate/major-vueuse-monorepo
• Merge into: main
• Upgrade @vueuse/nuxt to ^12.0.0

chore(deps): update dependency eslint to v9

• Schedule: ["at any time"]
• Branch name: renovate/major-eslint-monorepo
• Merge into: main
• Upgrade eslint to ^9.0.0

fix(deps): update dependency pathe to v2

• Schedule: ["at any time"]
• Branch name: renovate/pathe-2.x
• Merge into: main
• Upgrade pathe to ^2.0.0

🚸 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 was generated by Mend Renovate. View the repository job log.

[dargmuesli]

I think it makes much sense to enable renovate, so that breaking updates can be found right away Without, after some time when someone updates manually they'd have to dig more to find which dependency update and version leads to issues.