Configure Renovate

[lucca-renovate]

Description

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

• Dockerfile (dockerfile)
• renovate.json (renovate-config-presets)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• 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.
• Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
• Run lock file maintenance (updates) early Monday mornings.
• Run Renovate on following schedule: before 9am every weekday,after 7pm every weekday,every weekend

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch and select the Retry/Rebase checkbox below. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

With your current configuration, Renovate will create 3 Pull Requests:

Pin mcr.microsoft.com/dotnet/aspnet Docker tag to e70c493 dockerfile stage

• Schedule: ["before 9am every weekday","after 7pm every weekday","every weekend"]
• Branch name: renovate/dockerfile-stage-pindigest
• Merge into: master
• Upgrade mcr.microsoft.com/dotnet/aspnet to sha256:e70c493f8af7f95bf459cb2b15c7e7a6173228929c2b7a9a6836b19377890e78

Pin mcr.microsoft.com/dotnet/sdk Docker tag to c8fdd06 dockerfile final

• Schedule: ["before 9am every weekday","after 7pm every weekday","every weekend"]
• Branch name: renovate/dockerfile-final-pindigest
• Merge into: master
• Upgrade mcr.microsoft.com/dotnet/sdk to sha256:c8fdd06e430de9f4ddd066b475ea350d771f341b77dd5ff4c2fafa748e3f2ef2

Update dotnet monorepo to v10 (major)

• Schedule: ["before 9am every weekday","after 7pm every weekday","every weekend"]
• Branch name: renovate/major-dotnet-monorepo
• Merge into: master
• Upgrade mcr.microsoft.com/dotnet/aspnet to sha256:8c0b6857eab7b2aa57884c839bf4678414606bd7d17370f18a842ac5cf414711
• Upgrade mcr.microsoft.com/dotnet/sdk to sha256:c0790639332692a0d56cdd81ed581cfd24d040d9839764c138994866df89a3b6

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

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Renovate Bot.