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.

📚 See our Reading List for relevant documentation you may be interested in reading.

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

---

Detected Package Files

• .github/actions/install/action.yml (github-actions)
• .github/workflows/ci.yml (github-actions)
• .github/workflows/congrats.yml (github-actions)
• .github/workflows/format.yml (github-actions)
• .github/workflows/prerelease.yml (github-actions)
• .github/workflows/release.yml (github-actions)
• package.json (npm)

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 Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.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
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs

---

What to Expect

With your current configuration, Renovate will create 31 Pull Requests:

Update dependency rollup to v3.30.0 [SECURITY]

• Branch name: renovate/npm-rollup-vulnerability
• Merge into: main
• Upgrade rollup to 3.30.0

Update dependency vite to v6 [SECURITY]

• Branch name: renovate/npm-vite-vulnerability
• Merge into: main
• Upgrade vite to ^6.0.0

Update dependency vitest to v3 [SECURITY]

• Branch name: renovate/npm-vitest-vulnerability
• Merge into: main
• Upgrade vitest to ^3.0.0

Update dependency @​rollup/plugin-commonjs to v25.0.8

• Schedule: ["at any time"]
• Branch name: renovate/rollup-plugin-commonjs-25.x-lockfile
• Merge into: main
• Upgrade @rollup/plugin-commonjs to 25.0.8

Update dependency @​rollup/plugin-typescript to v11.1.6

• Schedule: ["at any time"]
• Branch name: renovate/rollup-plugin-typescript-11.x-lockfile
• Merge into: main
• Upgrade @rollup/plugin-typescript to 11.1.6

Update dependency @​astrojs/compiler to v2.13.1

• Schedule: ["at any time"]
• Branch name: renovate/astrojs-compiler-2.x-lockfile
• Merge into: main
• Upgrade @astrojs/compiler to 2.13.1

Update dependency @​biomejs/biome to v1.9.4

• Schedule: ["at any time"]
• Branch name: renovate/biomejs-biome-1.x
• Merge into: main
• Upgrade @biomejs/biome to 1.9.4

Update dependency @​changesets/cli to v2.31.0

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

Update dependency @​types/node to v20.19.43

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

Update dependency @​vitest/ui to ^0.34.0

• Schedule: ["at any time"]
• Branch name: renovate/vitest-monorepo
• Merge into: main
• Upgrade @vitest/ui to ^0.34.0

Update dependency eslint to v9.39.5

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

Update dependency eslint-plugin-regexp to v2.10.0

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-regexp-2.x-lockfile
• Merge into: main
• Upgrade eslint-plugin-regexp to 2.10.0

Update dependency prettier to v3.9.5

• Schedule: ["at any time"]
• Branch name: renovate/prettier-3.x-lockfile
• Merge into: main
• Upgrade prettier to 3.9.5

Update dependency sass-formatter to ^0.8.0

• Schedule: ["at any time"]
• Branch name: renovate/sass-formatter-0.x
• Merge into: main
• Upgrade sass-formatter to ^0.8.0

Update dependency tslib to v2.8.1

• Schedule: ["at any time"]
• Branch name: renovate/tslib-2.x-lockfile
• Merge into: main
• Upgrade tslib to 2.8.1

Update dependency typescript to v5.9.3

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

Update dependency typescript-eslint to v8.63.0

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

Update pnpm to v8.15.9

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

Update actions/checkout action to v7

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

Update actions/setup-node action to v6

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

Update dependency @​astrojs/compiler to v4

• Schedule: ["at any time"]
• Branch name: renovate/astrojs-compiler-4.x
• Merge into: main
• Upgrade @astrojs/compiler to ^4.0.0

Update dependency @​biomejs/biome to v2

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

Update dependency @​rollup/plugin-commonjs to v29

• Schedule: ["at any time"]
• Branch name: renovate/rollup-plugin-commonjs-29.x
• Merge into: main
• Upgrade @rollup/plugin-commonjs to ^29.0.0

Update dependency @​rollup/plugin-typescript to v12

• Schedule: ["at any time"]
• Branch name: renovate/rollup-plugin-typescript-12.x
• Merge into: main
• Upgrade @rollup/plugin-typescript to ^12.0.0

Update dependency @​types/node to v24

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

Update dependency @​vitest/ui to v4

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

Update dependency eslint to v10

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

Update dependency eslint-plugin-regexp to v3

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-regexp-3.x
• Merge into: main
• Upgrade eslint-plugin-regexp to ^3.0.0

Update dependency typescript to v7

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

Update pnpm to v11

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

Update pnpm/action-setup action to v6

• Schedule: ["at any time"]
• Branch name: renovate/pnpm-action-setup-6.x
• Merge into: main
• Upgrade pnpm/action-setup to v6

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8087132

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR