Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Sep 24, 2025

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

  • 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 12 Pull Requests:

Update dependency @mdx-js/react to v3.1.1
  • Schedule: ["at any time"]
  • Branch name: renovate/mdx-monorepo
  • Merge into: dev
  • Upgrade @mdx-js/react to 3.1.1
Update dependency redoc to v2.5.1
  • Schedule: ["at any time"]
  • Branch name: renovate/redoc-2.x-lockfile
  • Merge into: dev
  • Upgrade redoc to 2.5.1
Update dependency styled-components to v6.1.19
  • Schedule: ["at any time"]
  • Branch name: renovate/styled-components-6.x-lockfile
  • Merge into: dev
  • Upgrade styled-components to 6.1.19
Update dependency @easyops-cn/docusaurus-search-local to ^0.52.0
Update dependency core-js to v3.46.0
  • Schedule: ["at any time"]
  • Branch name: renovate/core-js-3.x-lockfile
  • Merge into: dev
  • Upgrade core-js to 3.46.0
Update dependency mobx to v6.15.0
  • Schedule: ["at any time"]
  • Branch name: renovate/mobx-6.x-lockfile
  • Merge into: dev
  • Upgrade mobx to 6.15.0
Update dependency redocusaurus to v2.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/redocusaurus-2.x-lockfile
  • Merge into: dev
  • Upgrade redocusaurus to 2.5.0
Update dependency sass to v1.93.2
  • Schedule: ["at any time"]
  • Branch name: renovate/sass-1.x-lockfile
  • Merge into: dev
  • Upgrade sass to 1.93.2
Update docusaurus monorepo to v3.9.1
Update dependency css-minimizer-webpack-plugin to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/css-minimizer-webpack-plugin-7.x
  • Merge into: dev
  • Upgrade css-minimizer-webpack-plugin to ^7.0.0
Update dependency framer-motion to v12
  • Schedule: ["at any time"]
  • Branch name: renovate/framer-motion-12.x
  • Merge into: dev
  • Upgrade framer-motion to ^12.0.0
Update react monorepo to v19 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-react-monorepo
  • Merge into: dev
  • 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.

@vercel
Copy link

vercel bot commented Sep 24, 2025

Unable to deploy a commit from a private repository on your GitHub organization to the SuperDev's projects team on Vercel, which is currently on the Hobby plan. In order to deploy, you can:

  • Make your repository public or
  • Upgrade to Pro. A Pro subscription is required to deploy from a private organization repository.

To read more about collaboration on Vercel, click here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant