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

• package.json (npm)
• pnpm-workspace.yaml (npm)
• renovate.json (renovate-config-presets)

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.
• 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 GitHub.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
• Group all minor and patch updates together.
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
• Schedule automerge for the first day of each month, before 4 AM.
• Automerge non-major upgrades for semver stable packages if they pass tests.
• Preserve (but continue to upgrade) any existing SemVer ranges.

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

chore(deps): update pnpm to v10.30.2

• Schedule: ["at any time"]
• Branch name: renovate/all-minor-patch
• Merge into: main
• Upgrade pnpm to 10.30.2

chore(deps): update dependency @​clack/prompts to v1

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

chore(deps): update dependency eslint to v10

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

chore(deps): update dependency lint-staged to v16

• Schedule: ["at any time"]
• Branch name: renovate/lint-staged-16.x
• Merge into: main
• Upgrade lint-staged 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 was generated by Mend Renovate. View the repository job log.