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/build_and_deploy.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
• 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.

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

chore(deps): update dependency @iconify-json/mdi to v1.1.62

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

chore(deps): update dependency postcss to v8.4.32

• Schedule: ["at any time"]
• Branch name: renovate/postcss-8.x-lockfile
• Merge into: main
• Upgrade postcss to 8.4.32

chore(deps): update dependency vite to v2.9.16

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

chore(deps): update dependency prettier to v2.8.8

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

chore(deps): update dependency prettier-plugin-tailwindcss to ^0.5.0

• Schedule: ["at any time"]
• Branch name: renovate/prettier-plugin-tailwindcss-0.x
• Merge into: main
• Upgrade prettier-plugin-tailwindcss to ^0.5.0

chore(deps): update dependency tailwindcss to v3.3.6

• Schedule: ["at any time"]
• Branch name: renovate/tailwindcss-3.x-lockfile
• Merge into: main
• Upgrade tailwindcss to 3.3.6

chore(deps): update dependency unplugin-icons to ^0.18.0

• Schedule: ["at any time"]
• Branch name: renovate/unplugin-icons-0.x
• Merge into: main
• Upgrade unplugin-icons to ^0.18.0

chore(deps): update pnpm/action-setup action to v2.4.0

• Schedule: ["at any time"]
• Branch name: renovate/pnpm-action-setup-2.x
• Merge into: main
• Upgrade pnpm/action-setup to v2.4.0

chore(deps): update vue monorepo to v3.3.11

• Schedule: ["at any time"]
• Branch name: renovate/vue-monorepo
• Merge into: main
• Upgrade @vue/compiler-sfc to 3.3.11
• Upgrade vue to 3.3.11

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

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

chore(deps): update dependency @​vitejs/plugin-vue to v4

• Schedule: ["at any time"]
• Branch name: renovate/vitejs-plugin-vue-4.x
• Merge into: main
• Upgrade @vitejs/plugin-vue to ^4.0.0

chore(deps): update dependency prettier to v3

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

chore(deps): update dependency vite to v5

• Schedule: ["at any time"]
• Branch name: renovate/vite-5.x
• Merge into: main
• Upgrade vite to ^5.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 has been generated by Mend Renovate. View repository job log here.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f9f2d8e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR