[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/publish.yml (github-actions)
• package.json (npm)
• .nvmrc (nvm)
• 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
• Run lock file maintenance (updates) early Monday mornings.
• Use semantic prefixes for commit messages and PR titles.
• Group known monorepo packages together.

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

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

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-6.x
• Merge into: master
• Upgrade actions/checkout to v6

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

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-node-6.x
• Merge into: master
• Upgrade actions/setup-node to v6

chore(deps): update dependency @​biomejs/biome to v2

• Schedule: ["at any time"]
• Branch name: renovate/biomejs-biome-2.x
• Merge into: master
• Upgrade @biomejs/biome to 2.3.11

chore(deps): update dependency lefthook to v2

• Schedule: ["at any time"]
• Branch name: renovate/lefthook-2.x
• Merge into: master
• Upgrade lefthook to ^2.0.0

chore(deps): update dependency release-it to v19

• Schedule: ["at any time"]
• Branch name: renovate/release-it-19.x
• Merge into: master
• Upgrade release-it to ^19.0.0

chore(deps): update node.js to v24

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

chore(deps): update vitest monorepo to v4 (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-vitest-monorepo
• Merge into: master
• Upgrade @vitest/coverage-v8 to ^4.0.0
• Upgrade @vitest/ui to ^4.0.0
• Upgrade vitest to ^4.0.0

chore(deps): lock file maintenance

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/lock-file-maintenance
• Merge into: master
• 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 was generated by Mend Renovate. View the repository job log.