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.yaml (github-actions)
• .github/workflows/release.yaml (github-actions)
• .yarn/sdks/eslint/package.json (npm)
• .yarn/sdks/prettier/package.json (npm)
• .yarn/sdks/typescript/package.json (npm)
• package.json (npm)
• packages/eslint-config/package.json (npm)
• packages/eslint-import-resolver-require/package.json (npm)
• packages/internal-test-utils/package.json (npm)
• packages/unused-files/package.json (npm)
• .nvmrc (nvm)

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 11 Pull Requests:

chore(deps): update dependency @​monoweave/plugin-github to v2.1.1

• Schedule: ["at any time"]
• Branch name: renovate/monoweave-plugin-github-2.x-lockfile
• Merge into: main
• Upgrade @monoweave/plugin-github to 2.1.1

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

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

chore(deps): update dependency ts-jest to v29.1.2

• Schedule: ["at any time"]
• Branch name: renovate/ts-jest-29.x-lockfile
• Merge into: main
• Upgrade ts-jest to 29.1.2

chore(deps): update dependency ts-node to v10.9.2

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

fix(deps): update dependency @​monoweave/cli to v1.2.1

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

fix(deps): update dependency clipanion to v4.0.0-rc.3

• Schedule: ["at any time"]
• Branch name: renovate/clipanion-4.x
• Merge into: main
• Upgrade clipanion to 4.0.0-rc.3

chore(deps): update dependency @​types/node to v20.12.2

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

chore(deps): update dependency lint-staged to v15.2.2

• Schedule: ["at any time"]
• Branch name: renovate/lint-staged-15.x-lockfile
• Merge into: main
• Upgrade lint-staged to 15.2.2

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

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

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

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

chore(deps): update dependency husky to v9

• Schedule: ["at any time"]
• Branch name: renovate/husky-9.x
• Merge into: main
• Upgrade husky to ^9.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.

[github-actions]

Package Release Preview

This pull request does not introduce any package version changes. If this is incorrect, please ensure that you are using conventional commit prefixes, or have provided a version file.