TryMudBlazor icon indicating copy to clipboard operation
TryMudBlazor copied to clipboard

Published 20 hours ago • verified publisher icon MudBlazor

Configure Renovate

Open renovate-bot opened this issue 7 months ago • 1 comments

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/build-test-trymudblazor.yml (github-actions)
  • .github/workflows/deploy-web-app-trymudblazor.yml (github-actions)
  • src/Try.Core/Try.Core.csproj (nuget)
  • src/Try.Tests/Try.Tests.csproj (nuget)
  • src/TryMudBlazor.Client/TryMudBlazor.Client.csproj (nuget)
  • src/TryMudBlazor.Server/TryMudBlazor.Server.csproj (nuget)
  • src/UserComponents/Try.UserComponents.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.
  • 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:

Update azure azure-sdk-for-net monorepo
  • Schedule: ["at any time"]
  • Branch name: renovate/azure-azure-sdk-for-net-monorepo
  • Merge into: main
  • Upgrade Azure.Identity to 1.13.2
  • Upgrade Azure.Storage.Blobs to 12.24.0
Update dependency Microsoft.DotNet.Arcade.Sdk to 9.0.0-beta.25164.2
  • Schedule: ["at any time"]
  • Branch name: renovate/microsoft.dotnet.arcade.sdk-9.x
  • Merge into: main
  • Upgrade Microsoft.DotNet.Arcade.Sdk to 9.0.0-beta.25164.2
Update dependency Microsoft.Net.Compilers.Razor.Toolset to 9.0.0-preview.25177.3
Update dotnet monorepo
Update dependency FluentValidation to 11.11.0
  • Schedule: ["at any time"]
  • Branch name: renovate/fluentvalidation-11.x
  • Merge into: main
  • Upgrade FluentValidation to 11.11.0
Update dependency Microsoft.NET.Test.Sdk to 17.13.0
  • Schedule: ["at any time"]
  • Branch name: renovate/vstest-monorepo
  • Merge into: main
  • Upgrade Microsoft.NET.Test.Sdk to 17.13.0
Update dependency NUnit to 4.3.2
  • Schedule: ["at any time"]
  • Branch name: renovate/nunit-4.x
  • Merge into: main
  • Upgrade NUnit to 4.3.2
Update dependency NUnit3TestAdapter to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/nunit3testadapter-5.x
  • Merge into: main
  • Upgrade NUnit3TestAdapter to 5.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.

❓ 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-bot avatar Mar 08 '25 22:03 renovate-bot