Configure Renovate

[renovate[bot]]

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

• Dockerfile (dockerfile)
• 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 12 Pull Requests:

chore(deps): update dependency autoprefixer to v10.4.16

• Schedule: ["at any time"]
• Branch name: renovate/autoprefixer-10.x-lockfile
• Merge into: main
• Upgrade autoprefixer to 10.4.16

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 eslint to v8.55.0

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

chore(deps): update dependency eslint-config-standard to v17.1.0

• Schedule: ["at any time"]
• Branch name: renovate/eslint-config-standard-17.x-lockfile
• Merge into: main
• Upgrade eslint-config-standard to 17.1.0

chore(deps): update dependency eslint-plugin-import to v2.29.1

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-import-2.x
• Merge into: main
• Upgrade eslint-plugin-import to 2.29.1

chore(deps): update dependency eslint-plugin-n to v15.7.0

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-n-15.x-lockfile
• Merge into: main
• Upgrade eslint-plugin-n to 15.7.0

chore(deps): update dependency eslint-plugin-promise to v6.1.1

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-promise-6.x
• Merge into: main
• Upgrade eslint-plugin-promise to 6.1.1

chore(deps): update dependency nuxt to v3.8.2

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

chore(deps): update dependency sass to v1.69.5

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

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 eslint-plugin-n to v16

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-n-16.x
• Merge into: main
• Upgrade eslint-plugin-n to ^16.0.0

chore(deps): update node.js to v20

• Schedule: ["at any time"]
• Branch name: renovate/node-20.x
• Merge into: main
• Upgrade node to 20-alpine

🚸 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[bot]]

⚠️ No Changeset found

Latest commit: 87da5b76b14e5bf9173f97f7d2a8642d763428b7

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