Configure Renovate

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

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)
• package.json (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.
• 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 (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.
• Set semantic commit type based on advanced rules
• Presets that harden security for shared GitHub Action Workflows
• Always widen peerDependencies and engines, while other types like dependencies, devDependencies are update-lockfile.
• Assign 📦 deps and 🤖 bot labels, and for major updates ⚠️ major
• Opt-in to refresh lock files once in a while
• Update CI images to use the latest LTS of Node.js
• Pin TypeScript to the same version used by @sanity/pkg-utils and @sanity/tsdoc
• Group various lint packages together.
• Group PostCSS packages together.
• Group all updates except major into its own PR, when possible.
• Workaround packages that are Pure ESM directly, or have started using transitive dependencies that are.
• Workaround how babel-plugin-react-compiler is publishing experimental versions on the latest tag, without this workaround renovate will downgrade the version to 0.0.0
• Dedupe lockfiles after updates for npm, pnpm, and yarn.
• Use curated presets maintained by Sanity. See docs for advanced usage.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to .github/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 15 Pull Requests:

chore(deps): update non-major

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/non-major
• Merge into: main
• Upgrade glob to ^7.2.3
• Upgrade js-yaml to ^3.14.1
• Upgrade minimist to ^1.2.8
• Upgrade ncipollo/release-action to b7eabc95ff50cbeeedec83973935c8f306dfcd0b
• Upgrade prettier to ^2.8.8

chore(deps): update pnpm to v10.17.1

• Schedule: ["* * 1 */12 *"]
• Branch name: renovate/corepack
• Merge into: main
• Upgrade pnpm to 10.17.1

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

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

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 actions/checkout action to v5

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

chore(deps): update actions/setup-node action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-node-5.x
• Merge into: main
• Upgrade actions/setup-node to v5

chore(deps): update dependency node to v22

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

chore(deps): update dependency prettier to v3

• Schedule: ["before 3am on the first day of the month"]
• Branch name: renovate/major-3-linters
• Merge into: main
• Upgrade prettier to ^3.6.2

fix(deps): Update dependency glob to v8

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/glob-8.x
• Merge into: main
• Upgrade glob to ^8.1.0

fix(deps): Update dependency glob to v9

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/glob-9.x
• Merge into: main
• Upgrade glob to ^9.3.5

fix(deps): Update dependency glob to v10

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/glob-10.x
• Merge into: main
• Upgrade glob to ^10.4.5

fix(deps): Update dependency glob to v11

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/glob-11.x
• Merge into: main
• Upgrade glob to ^11.0.3

fix(deps): Update dependency js-yaml to v4

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/js-yaml-4.x
• Merge into: main
• Upgrade js-yaml to ^4.1.0

fix(deps): Update dependency ndjson to v2

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/ndjson-2.x
• Merge into: main
• Upgrade ndjson to ^2.0.0

chore(deps): lock file maintenance

• Schedule: ["* * 1 */12 *"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions

🚸 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 using a curated preset maintained by . View repository job log here