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.yml (github-actions)
• .github/workflows/publish.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.
• 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
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
• 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.
• Run lock file maintenance (updates) early Monday mornings.
• Show OpenSSF badge on pull requests.
• Use semantic prefixes for commit messages and PR titles.
• Org-wide Renovate preset for midnightntwrk. Supply-chain hardened.
• Run Renovate on following schedule: before 7am on Monday

🔡 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): pin dependencies

• Schedule: ["before 7am on Monday"]
• Branch name: renovate/pin-dependencies
• Merge into: main
• Pin @types/cross-spawn to 6.0.6
• Pin @types/fs-extra to 11.0.4
• Pin @types/mustache to 4.2.6
• Pin @types/node to 20.19.23
• Pin @types/prompts to 2.4.9
• Pin @types/update-notifier to 6.0.8
• Pin @types/validate-npm-package-name to 4.0.2
• Pin @typescript-eslint/eslint-plugin to 8.57.0
• Pin @typescript-eslint/parser to 8.57.0
• Pin @vitest/coverage-v8 to 4.0.18
• Upgrade actions/checkout to f43a0e5ff2bd294095638e18286ca9a3d1956744
• Upgrade actions/checkout to 34e114876b0b11c390a56381ad16ebd13914f8d5
• Upgrade actions/setup-node to 3235b876344d2a9aa001b8d1453c930bba69e610
• Upgrade actions/setup-node to 49933ea5288caeca8642d1e84afbd3f7d6820020
• Pin eslint to 10.0.3
• Pin eslint-config-prettier to 10.1.8
• Pin prettier to 3.8.1
• Pin typescript to 5.9.3
• Pin vitest to 4.0.18

chore(deps): update non-major dependencies

• Schedule: ["before 7am on Monday"]
• Branch name: renovate/non-major-deps
• Merge into: main
• Upgrade @types/node to ^20.19.23
• Upgrade @vitest/coverage-v8 to ^4.1.2
• Upgrade fs-extra to 11.3.4
• Upgrade semver to 7.7.4

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

• Schedule: ["before 7am on Monday"]
• Branch name: renovate/actions-checkout-6.x
• Merge into: main
• Upgrade actions/checkout to de0fac2e4500dabe0009e67214ff5f5447ce83dd

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

• Schedule: ["before 7am on Monday"]
• Branch name: renovate/actions-setup-node-6.x
• Merge into: main
• Upgrade actions/setup-node to 53b83947a5a98c8d113130e565377fae1a50d02f

chore(deps): update dependency node to v24

• Schedule: ["before 7am on Monday"]
• Branch name: renovate/node-24.x
• Merge into: main
• Upgrade node to 24
• Upgrade @types/node to ^24.0.0

chore(deps): update dependency typescript to v6

• Schedule: ["before 7am on Monday"]
• Branch name: renovate/typescript-6.x
• Merge into: main
• Upgrade typescript to ^6.0.0

fix(deps): update dependency chalk to v5

• Schedule: ["before 7am on Monday"]
• Branch name: renovate/chalk-5.x
• Merge into: main
• Upgrade chalk to ^5.0.0

fix(deps): update dependency commander to v14

• Schedule: ["before 7am on Monday"]
• Branch name: renovate/commander-14.x
• Merge into: main
• Upgrade commander to ^14.0.0

fix(deps): update dependency ora to v9

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

fix(deps): update dependency validate-npm-package-name to v6

• Schedule: ["before 7am on Monday"]
• Branch name: renovate/validate-npm-package-name-6.x
• Merge into: main
• Upgrade validate-npm-package-name to ^6.0.0

chore(deps): lock file maintenance

• Schedule: ["before 7am on the first day of the month"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions

🚸 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.