Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Configure Renovate #3

Merged
merged 1 commit into from
Mar 28, 2024
Merged

chore: Configure Renovate #3

merged 1 commit into from
Mar 28, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 17, 2023

Mend 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

  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • 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 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.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Rebase existing PRs any time the base branch has been updated.
  • Disable Renovate Dependency Dashboard creation.
  • If automerging, push the new commit directly to the base branch (no PR).
  • Automerge patch upgrades if they pass tests.
  • Automerge patch and minor upgrades if they pass tests.
  • Parse Ruby Gemspec files
  • Do not upgrade perl version. See: https://github.com/renovatebot/renovate/discussions/23472 and https://github.com/renovatebot/renovate/discussions/23762

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

fix(deps): update dependency @mdx-js/react to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/major-mdx-monorepo
  • Merge into: main
  • Upgrade @mdx-js/react to ^3.0.0
fix(deps): update dependency clsx to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/clsx-2.x
  • Merge into: main
  • Upgrade clsx to ^2.0.0
fix(deps): update dependency prism-react-renderer to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/prism-react-renderer-2.x
  • Merge into: main
  • Upgrade prism-react-renderer to ^2.0.0
fix(deps): update docusaurus monorepo to v3 (major)
fix(deps): update react monorepo to v18 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-react-monorepo
  • Merge into: main
  • Upgrade react to ^18.0.0
  • Upgrade react-dom to ^18.0.0

❓ 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 has been generated by Mend Renovate. View repository job log here.

@davidjgoss davidjgoss merged commit 07f075d into main Mar 28, 2024
@davidjgoss davidjgoss deleted the renovate/configure branch March 28, 2024 18:20
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.

None yet

1 participant