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

Configure Renovate #138

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Configure Renovate #138

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 6, 2022

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)
  • .travis.yml (travis)

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 (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 7 Pull Requests:

chore(deps): update dependency semantic-release to v19 [security]
  • Branch name: renovate/npm-semantic-release-vulnerability
  • Merge into: master
  • Upgrade semantic-release to 19.0.3
chore(deps): update react monorepo
  • Schedule: ["at any time"]
  • Branch name: renovate/react-monorepo
  • Merge into: master
  • Upgrade @types/react to 17.0.83
  • Upgrade @types/react-dom to 17.0.26
chore(deps): update dependency typescript to v4.9.5
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-4.x
  • Merge into: master
  • Upgrade typescript to 4.9.5
chore(deps): update dependency typescript to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x
  • Merge into: master
  • Upgrade typescript to 5.7.2
chore(deps): update jest monorepo to v29 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jest-monorepo
  • Merge into: master
  • Upgrade @types/jest to 29.5.14
  • Upgrade jest to 29.7.0
  • Upgrade ts-jest to 29.2.5
chore(deps): update react monorepo to v19 (major)
chore(deps): update testing-library monorepo (major)

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

@renovate renovate bot force-pushed the renovate/configure branch from fd1351b to bb7d0fc Compare December 14, 2023 20:57
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.

0 participants