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

• gradle.properties (gradle)
• bintrayv1.gradle (gradle)
• installv1.gradle (gradle)
• settings.gradle (gradle)
• build.gradle (gradle)
• sdk/build.gradle (gradle)
• gradle/wrapper/gradle-wrapper.properties (gradle-wrapper)

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.
• 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 v3.6.4

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

Update dependency androidx.appcompat:appcompat to v1.7.0

• Schedule: ["at any time"]
• Branch name: renovate/androidx.appcompat-appcompat-1.x
• Merge into: development
• Upgrade androidx.appcompat:appcompat to 1.7.0

Update dependency androidx.test.espresso:espresso-core to v3.6.1

• Schedule: ["at any time"]
• Branch name: renovate/androidx.test.espresso-espresso-core-3.x
• Merge into: development
• Upgrade androidx.test.espresso:espresso-core to 3.6.1

Update dependency androidx.test.ext:junit to v1.2.1

• Schedule: ["at any time"]
• Branch name: renovate/androidx.test.ext-junit-1.x
• Merge into: development
• Upgrade androidx.test.ext:junit to 1.2.1

Update dependency com.android.volley:volley to v1.2.1

• Schedule: ["at any time"]
• Branch name: renovate/com.android.volley-volley-1.x
• Merge into: development
• Upgrade com.android.volley:volley to 1.2.1

Update dependency junit:junit to v4.13.2

• Schedule: ["at any time"]
• Branch name: renovate/junit-junit-4.x
• Merge into: development
• Upgrade junit:junit to 4.13.2

Update dependency com.android.tools.build:gradle to v8

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

Update dependency gradle to v8

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

Update dependency org.json:json to v20250107

• Schedule: ["at any time"]
• Branch name: renovate/org.json-json-20250107.x
• Merge into: development
• Upgrade org.json:json to 20250107

🚸 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.jfrog.bintray.gradle:gradle-bintray-plugin

Files affected: 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 was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f7eace6

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