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

• docker-compose.yml (docker-compose)
• Dockerfile (dockerfile)
• 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.

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

Update dependency vite to v5.4.20 [SECURITY]

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

Update dependency @react-sigma/core to v5.0.4

• Schedule: ["at any time"]
• Branch name: renovate/react-sigma-core-5.x-lockfile
• Merge into: main
• Upgrade @react-sigma/core to 5.0.4

Update dependency @react-sigma/graph-search to v5.0.4

• Schedule: ["at any time"]
• Branch name: renovate/react-sigma-graph-search-5.x-lockfile
• Merge into: main
• Upgrade @react-sigma/graph-search to 5.0.4

Update dependency @react-sigma/layout-circular to v5.0.4

• Schedule: ["at any time"]
• Branch name: renovate/react-sigma-layout-circular-5.x-lockfile
• Merge into: main
• Upgrade @react-sigma/layout-circular to 5.0.4

Update dependency @react-sigma/layout-core to v5.0.4

• Schedule: ["at any time"]
• Branch name: renovate/react-sigma-layout-core-5.x-lockfile
• Merge into: main
• Upgrade @react-sigma/layout-core to 5.0.4

Update dependency @react-sigma/layout-forceatlas2 to v5.0.4

• Schedule: ["at any time"]
• Branch name: renovate/react-sigma-layout-forceatlas2-5.x-lockfile
• Merge into: main
• Upgrade @react-sigma/layout-forceatlas2 to 5.0.4

Update dependency @react-sigma/minimap to v5.0.5

• Schedule: ["at any time"]
• Branch name: renovate/react-sigma-minimap-5.x-lockfile
• Merge into: main
• Upgrade @react-sigma/minimap to 5.0.5

Update dependency @​sigma/node-image to v3.0.0

• Schedule: ["at any time"]
• Branch name: renovate/sigma-node-image-3.x-lockfile
• Merge into: main
• Upgrade @sigma/node-image to 3.0.0

Update dependency autoprefixer to v10.4.21

• Schedule: ["at any time"]
• Branch name: renovate/autoprefixer-10.x-lockfile
• Merge into: main
• Upgrade autoprefixer to 10.4.21

Update dependency eslint-plugin-react-refresh to v0.4.24

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-react-refresh-0.x-lockfile
• Merge into: main
• Upgrade eslint-plugin-react-refresh to 0.4.24

Update dependency react-select to v5.10.2

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

Update dependency sigma to v3.0.2

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

Update dependency tailwindcss to v3.4.18

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

Update react monorepo

• Schedule: ["at any time"]
• Branch name: renovate/react-monorepo
• Merge into: main
• Upgrade @types/react to 18.3.26
• Upgrade @types/react-dom to 18.3.7
• Upgrade eslint-plugin-react-hooks to 5.2.0

Update dependency @​types/node to v22.18.11

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

Update dependency @​vitejs/plugin-react to v4.7.0

• Schedule: ["at any time"]
• Branch name: renovate/vitejs-plugin-react-4.x-lockfile
• Merge into: main
• Upgrade @vitejs/plugin-react to 4.7.0

Update dependency dotenv to v16.6.1

• Schedule: ["at any time"]
• Branch name: renovate/dotenv-16.x-lockfile
• Merge into: main
• Upgrade dotenv to 16.6.1

Update dependency globals to v15.15.0

• Schedule: ["at any time"]
• Branch name: renovate/globals-15.x-lockfile
• Merge into: main
• Upgrade globals to 15.15.0

Update dependency graphology to ^0.26.0

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

Update dependency graphology-metrics to v2.4.0

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

Update dependency minisearch to v7.2.0

• Schedule: ["at any time"]
• Branch name: renovate/minisearch-7.x-lockfile
• Merge into: main
• Upgrade minisearch to 7.2.0

Update dependency postcss to v8.5.6

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

Update dependency react-icons to v5.5.0

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

Update dependency typescript to ~5.9.0

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

Update dependency typescript-eslint to v8.46.2

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

Update dependency wrangler to v4.43.0

• Schedule: ["at any time"]
• Branch name: renovate/wrangler-4.x-lockfile
• Merge into: main
• Upgrade wrangler to 4.43.0

Update eslint monorepo to v9.38.0

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

Update dependency @​vitejs/plugin-react to v5

• Schedule: ["at any time"]
• Branch name: renovate/vitejs-plugin-react-5.x
• Merge into: main
• Upgrade @vitejs/plugin-react to ^5.0.0

Update dependency dotenv to v17

• Schedule: ["at any time"]
• Branch name: renovate/dotenv-17.x
• Merge into: main
• Upgrade dotenv to ^17.0.0

Update dependency globals to v16

• Schedule: ["at any time"]
• Branch name: renovate/globals-16.x
• Merge into: main
• Upgrade globals to ^16.0.0

Update dependency tailwindcss to v4

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

Update react monorepo (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-react-monorepo
• Merge into: main
• Upgrade @types/react to ^19.0.0
• Upgrade @types/react-dom to ^19.0.0
• Upgrade eslint-plugin-react-hooks to ^7.0.0
• Upgrade react to ^19.0.0
• Upgrade react-dom to ^19.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.

[sourcery-ai]

Reviewer's Guide

This PR adds a new renovate.json configuration file to onboard Renovate with default presets—defining update schedules, grouping rules, commit conventions, dashboards, badges, ignored paths, and branch limits for automated dependency updates.

File-Level Changes

Change	Details	Files
Add Renovate configuration file for dependency management	Create renovate.json with default preset settings Enable dependency dashboard, merge confidence badges, and semantic commits Specify detected package types and ignored directories Configure update schedules, branch hourly limits, and PR grouping rules	renovate.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.