chore: Configure Renovate - autoclosed

[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/release.yml (github-actions)
• .github/workflows/test.yml (github-actions)
• .github/workflows/update-html-data.yml (github-actions)
• extensions/vscode/package.json (npm)
• package.json (npm)
• packages/component-meta/package.json (npm)
• packages/component-type-helpers/package.json (npm)
• packages/language-core/package.json (npm)
• packages/language-plugin-pug/package.json (npm)
• packages/language-server/package.json (npm)
• packages/language-service/package.json (npm)
• packages/tsc/package.json (npm)
• packages/typescript-plugin/package.json (npm)
• test-workspace/package.json (npm)

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.
• Show all Merge Confidence badges for pull requests.
• Use semantic prefixes for commit messages and PR titles.
• 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.
• Use curated list of recommended non-monorepo package groupings.
• Group known monorepo packages together.
• Use Ray's Best Practice configuration from so1ve/renovate-config
• Create a Dependency Dashboard as Issue, listing all upgrades
• Open new PRs automatically. You can manually trigger PRs from the Dependency Dashboard, those will be opened once renovate runs again (once every hour)
• Label all PRs with renovate
• Use semantic commit messages for all upgrades
• Open a maximum of 10 PRs concurrently
• Automatically set reviewers from CODEOWNERS

🔡 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 3 Pull Requests:

chore(deps): update all non-major dependencies

• Schedule: ["at any time"]
• Branch name: renovate/all-minor-patch
• Merge into: master
• Upgrade @types/vscode to 1.86.0
• Upgrade @vue/compiler-dom to 3.4.15
• Upgrade @vue/compiler-sfc to 3.4.15
• Upgrade @vue/shared to 3.4.15
• Upgrade vscode-html-languageservice to 5.1.2
• Upgrade vue to 3.4.15

chore(deps): update dependency vue2 to v3

• Schedule: ["at any time"]
• Branch name: renovate/major-vue-monorepo
• Merge into: master
• Upgrade vue2 to 3.4

chore(deps): lock file maintenance

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

---

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

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.