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

• android/build.gradle (gradle)
• example/android/gradle.properties (gradle)
• example/android/settings.gradle (gradle)
• example/android/build.gradle (gradle)
• example/android/app/build.gradle (gradle)
• android/gradle/wrapper/gradle-wrapper.properties (gradle-wrapper)
• example/android/gradle/wrapper/gradle-wrapper.properties (gradle-wrapper)
• example/package.json (npm)
• 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.

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

Update dependency com.android.tools.build:gradle to v1.5.0

• Schedule: ["at any time"]
• Branch name: renovate/com.android.tools.build-gradle-1.x
• Merge into: master
• Upgrade com.android.tools.build:gradle to 1.5.0

Update dependency gradle to v2.14.1

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

Update dependency react-native to ^0.73.0

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

Update dependency babel-eslint to v10

• Schedule: ["at any time"]
• Branch name: renovate/babel-eslint-10.x
• Merge into: master
• Upgrade babel-eslint to ^10.0.0

Update dependency com.android.tools.build:gradle to v2.3.3

• Schedule: ["at any time"]
• Branch name: renovate/com.android.tools.build-gradle-2.x
• Merge into: master
• Upgrade com.android.tools.build:gradle to 2.3.3

Update dependency eslint to v8

• Schedule: ["at any time"]
• Branch name: renovate/eslint-8.x
• Merge into: master
• Upgrade eslint to ^8.0.0

Update dependency eslint-plugin-react to v7

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

Update dependency gradle to v8

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

Update dependency react to v18

• Schedule: ["at any time"]
• Branch name: renovate/major-react-monorepo
• Merge into: master
• Upgrade react to ^18.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.

---

Warning

Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR.

• Failed to look up maven package com.android.support:appcompat-v7
• Failed to look up maven package com.android.support:design

Files affected: android/build.gradle, example/android/app/build.gradle

---

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: b07fa8a

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