Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

Renovate will begin keeping your dependencies up-to-date only once you merge this Pull Request.
If you close this Pull Request unmerged, then Renovate will be disabled.

If you have any questions, try reading our Docs, particularly the Getting Started section.
You can post questions in our Config Help repository or @ the app author @rarkins in this PR and he'll probably see it.

---

Detected Package Files

• src/Promitor.Scraper/Dockerfile (docker)
• src/Promitor.Scraper.Tests.Unit/Promitor.Scraper.Tests.Unit.csproj (nuget)
• src/Promitor.Scraper/Promitor.Scraper.csproj (nuget)

Configuration Summary

Based on the currently configured presets, Renovate will:

• Start dependency updates once this Configure Renovate PR is merged or closed
• Separate major versions of dependencies into individual branches/PRs
• Do not separate patch and minor upgrades into separate PRs for the same dependency
• Upgrade to unstable versions only if the existing version is unstable
• Raise PRs immediately (after branch is created)
• Use renovate/ as prefix for all branch names
• If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
• Keep existing branches updated even when not scheduled
• Disable automerging feature - wait for humans to merge all PRs
• Ignore node_modules, bower_components, and various test/tests directories
• Update existing lock files only when package.json is modified
• Autodetect whether to pin dependencies or maintain ranges
• Rate limit PR creation to a maximum of two per hour
• Limit to maximum 20 concurrent Renovate PRs at any time
• Preconfigure dependencies where an odd major version indicates unstable (Docker-only)

Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch and this Pull Request description will be updated the next time Renovate runs. Try to use Config Presets (the extends array) when possible rather than raw config, as then this PR will be able to more accurately describe your settings.

---

What to Expect

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

1. Pin Docker digests

• Branch name: renovate-docker-digests-pin
• Pins microsoft/aspnetcore to 5f9647
• Pins microsoft/dotnet to bd00a3

2. Update dependency Microsoft.AspNetCore.All to v2.1.0

• Branch name: renovate-microsoft.aspnetcore.all-2.x
• Upgrades Microsoft.AspNetCore.All in nuget from 2.0.0 to 2.1.0

3. Update dependency Microsoft.Azure.Management.Monitor to v0.20.0-preview

• Branch name: renovate-microsoft.azure.management.monitor-0.x
• Upgrades Microsoft.Azure.Management.Monitor in nuget from 0.19.1-preview to 0.20.0-preview

4. Update dependency Microsoft.Rest.ClientRuntime.Azure.Authentication to v2.3.3

• Branch name: renovate-microsoft.rest.clientruntime.azure.authentication-2.x
• Upgrades Microsoft.Rest.ClientRuntime.Azure.Authentication in nuget from 2.3.2 to 2.3.3

5. Update dependency Prometheus.Client.Owin to v1.5.0

• Branch name: renovate-prometheus.client.owin-1.x
• Upgrades Prometheus.Client.Owin in nuget from 1.4.0 to 1.5.0

6. Update dependency Swashbuckle.AspNetCore to v2.5.0

• Branch name: renovate-swashbuckle.aspnetcore-2.x
• Upgrades Swashbuckle.AspNetCore in nuget from 2.1.0 to 2.5.0

7. Update dependency YamlDotNet to v4.3.2

• Branch name: renovate-yamldotnet-4.x
• Upgrades YamlDotNet in nuget from 4.3.1 to 4.3.2

8. Update microsoft/dotnet Docker tag to v2.1-sdk

• Branch name: renovate-docker-microsoft-dotnet-2.x
• Upgrades microsoft/dotnet from undefined to 2.1-sdk

---

---

This PR has been generated by Renovate Bot.