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

• .github/workflows/main.yml (github-actions)
• .github/workflows/release-drafter.yml (github-actions)
• .github/workflows/release-nuget.yml (github-actions)
• src/Appium.Net/Appium.Net.csproj (nuget)
• test/integration/Appium.Net.Integration.Tests.csproj (nuget)

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

chore(deps): update dotnet monorepo

• Schedule: ["at any time"]
• Branch name: renovate/dotnet-monorepo
• Merge into: main
• Upgrade System.Drawing.Common to 8.0.21
• Upgrade System.Text.Json to 9.0.10

chore(deps): update dependency nunit to 4.4.0

• Schedule: ["at any time"]
• Branch name: renovate/nunit-4.x
• Merge into: main
• Upgrade NUnit to 4.4.0

chore(deps): update dependency nunit.analyzers to 4.10.0

• Schedule: ["at any time"]
• Branch name: renovate/nunit.analyzers-4.x
• Merge into: main
• Upgrade NUnit.Analyzers to 4.10.0

chore(deps): update dependency selenium.webdriver to 4.37.0

• Schedule: ["at any time"]
• Branch name: renovate/selenium.webdriver-4.x
• Merge into: main
• Upgrade Selenium.WebDriver to 4.37.0

chore(deps): update actions/setup-dotnet action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-dotnet-5.x
• Merge into: main
• Upgrade actions/setup-dotnet to v5

chore(deps): update dependency microsoft.net.test.sdk to v18

• Schedule: ["at any time"]
• Branch name: renovate/major-vstest-monorepo
• Merge into: main
• Upgrade Microsoft.NET.Test.Sdk to 18.0.0

chore(deps): update dependency nunit3testadapter to v5

• Schedule: ["at any time"]
• Branch name: renovate/nunit3testadapter-5.x
• Merge into: main
• Upgrade NUnit3TestAdapter to 5.2.0

chore(deps): update dependency system.drawing.common to v9

• Schedule: ["at any time"]
• Branch name: renovate/major-dotnet-monorepo
• Merge into: main
• Upgrade System.Drawing.Common to 9.0.10

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

[Dor-bl]

I would like to first checkout how dependabot is doing before moving to renovate bot

[laolubenson]

@Dor-bl can this be closed? Or do you still renovate as a successor

[Dor-bl]

We can close this one. Dependabot does the work for now.