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/codeql-analysis.yml (github-actions)
• .github/workflows/main.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.
• 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 35 Pull Requests:

chore(deps): replace dependency npm-run-all with npm-run-all2 ^5.0.0

• Schedule: ["at any time"]
• Branch name: renovate/npm-run-all-replacement
• Merge into: master
• Upgrade npm-run-all to ^5.0.0

chore(deps): replace dependency rollup-plugin-json with @​rollup/plugin-json ^4.0.0

• Schedule: ["at any time"]
• Branch name: renovate/rollup-plugin-json-replacement
• Merge into: master
• Upgrade rollup-plugin-json to ^4.0.0

chore(deps): update dependency @testing-library/react to v11.2.7

• Schedule: ["at any time"]
• Branch name: renovate/testing-library-monorepo
• Merge into: master
• Upgrade @testing-library/react to 11.2.7

chore(deps): update dependency common-tags to v1.8.2

• Schedule: ["at any time"]
• Branch name: renovate/common-tags-1.x-lockfile
• Merge into: master
• Upgrade common-tags to 1.8.2

chore(deps): update dependency pinst to v2.1.6

• Schedule: ["at any time"]
• Branch name: renovate/pinst-2.x-lockfile
• Merge into: master
• Upgrade pinst to 2.1.6

chore(deps): update react monorepo

• Schedule: ["at any time"]
• Branch name: renovate/react-monorepo
• Merge into: master
• Upgrade @types/react to 17.0.87
• Upgrade react to 17.0.2
• Upgrade react-dom to 17.0.2
• Upgrade react-test-renderer to 17.0.2

chore(deps): update babel monorepo

• Schedule: ["at any time"]
• Branch name: renovate/babel-monorepo
• Merge into: master
• Upgrade @babel/core to 7.27.4
• Upgrade @babel/preset-env to 7.27.2
• Upgrade @babel/preset-react to 7.27.1
• Upgrade @babel/preset-typescript to 7.27.1

chore(deps): update dependency bundlesize to ^0.18.0

• Schedule: ["at any time"]
• Branch name: renovate/bundlesize-0.x
• Merge into: master
• Upgrade bundlesize to ^0.18.0

chore(deps): update dependency domhandler to v4.3.1

• Schedule: ["at any time"]
• Branch name: renovate/domhandler-4.x-lockfile
• Merge into: master
• Upgrade domhandler to 4.3.1

chore(deps): update dependency husky to v5.2.0

• Schedule: ["at any time"]
• Branch name: renovate/husky-5.x-lockfile
• Merge into: master
• Upgrade husky to 5.2.0

chore(deps): update dependency prettier to v2.8.8

• Schedule: ["at any time"]
• Branch name: renovate/prettier-2.x-lockfile
• Merge into: master
• Upgrade prettier to 2.8.8

chore(deps): update dependency pretty-quick to v3.3.1

• Schedule: ["at any time"]
• Branch name: renovate/pretty-quick-3.x-lockfile
• Merge into: master
• Upgrade pretty-quick to 3.3.1

chore(deps): update dependency rollup to v1.32.1

• Schedule: ["at any time"]
• Branch name: renovate/rollup-1.x-lockfile
• Merge into: master
• Upgrade rollup to 1.32.1

chore(deps): update dependency rollup-plugin-terser to v5.3.1

• Schedule: ["at any time"]
• Branch name: renovate/rollup-plugin-terser-5.x-lockfile
• Merge into: master
• Upgrade rollup-plugin-terser to 5.3.1

chore(deps): update dependency rollup-plugin-typescript2 to ^0.36.0

• Schedule: ["at any time"]
• Branch name: renovate/rollup-plugin-typescript2-0.x
• Merge into: master
• Upgrade rollup-plugin-typescript2 to ^0.36.0

chore(deps): update dependency typescript to v4.9.5

• Schedule: ["at any time"]
• Branch name: renovate/typescript-4.x-lockfile
• Merge into: master
• Upgrade typescript to 4.9.5

fix(deps): update dependency html-entities to v2.6.0

• Schedule: ["at any time"]
• Branch name: renovate/html-entities-2.x-lockfile
• Merge into: master
• Upgrade html-entities to 2.6.0

fix(deps): update dependency htmlparser2 to v6.1.0

• Schedule: ["at any time"]
• Branch name: renovate/htmlparser2-6.x-lockfile
• Merge into: master
• Upgrade htmlparser2 to 6.1.0

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

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

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

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

chore(deps): update dependency @testing-library/react to v16

• Schedule: ["at any time"]
• Branch name: renovate/major-testing-library-monorepo
• Merge into: master
• Upgrade @testing-library/react to ^16.0.0

chore(deps): update dependency domhandler to v5

• Schedule: ["at any time"]
• Branch name: renovate/domhandler-5.x
• Merge into: master
• Upgrade domhandler to ^5.0.0

chore(deps): update dependency husky to v9

• Schedule: ["at any time"]
• Branch name: renovate/husky-9.x
• Merge into: master
• Upgrade husky to ^9.0.0

chore(deps): update dependency jest to v29

• Schedule: ["at any time"]
• Branch name: renovate/major-jest-monorepo
• Merge into: master
• Upgrade jest to ^29.0.0

chore(deps): update dependency node to v22

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

chore(deps): update dependency pinst to v3

• Schedule: ["at any time"]
• Branch name: renovate/pinst-3.x
• Merge into: master
• Upgrade pinst to ^3.0.0

chore(deps): update dependency prettier to v3

• Schedule: ["at any time"]
• Branch name: renovate/prettier-3.x
• Merge into: master
• Upgrade prettier to ^3.0.0

chore(deps): update dependency pretty-quick to v4

• Schedule: ["at any time"]
• Branch name: renovate/pretty-quick-4.x
• Merge into: master
• Upgrade pretty-quick to ^4.0.0

chore(deps): update dependency rimraf to v6

• Schedule: ["at any time"]
• Branch name: renovate/rimraf-6.x
• Merge into: master
• Upgrade rimraf to ^6.0.0

chore(deps): update dependency rollup to v4

• Schedule: ["at any time"]
• Branch name: renovate/rollup-4.x
• Merge into: master
• Upgrade rollup to ^4.0.0

chore(deps): update dependency rollup-plugin-terser to v7

• Schedule: ["at any time"]
• Branch name: renovate/rollup-plugin-terser-7.x
• Merge into: master
• Upgrade rollup-plugin-terser to ^7.0.0

chore(deps): update dependency typescript to v5

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

chore(deps): update github/codeql-action action to v3

• Schedule: ["at any time"]
• Branch name: renovate/github-codeql-action-3.x
• Merge into: master
• Upgrade github/codeql-action to v3

chore(deps): update react monorepo to v19 (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-react-monorepo
• Merge into: master
• Upgrade @types/react to ^19.0.0
• Upgrade react to ^19.0.0
• Upgrade react-dom to ^19.0.0
• Upgrade react-test-renderer to ^19.0.0

fix(deps): update dependency htmlparser2 to v10

• Schedule: ["at any time"]
• Branch name: renovate/htmlparser2-10.x
• Merge into: master
• Upgrade htmlparser2 to ^10.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 was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5b01ff8

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.

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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.