chore: 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/codeql.yml (github-actions)
• .github/workflows/publish_nuget.yml (github-actions)
• Directory.Build.props (nuget)
• MessagePack.NodaTime.Tests/MessagePack.NodaTime.Tests.csproj (nuget)
• MessagePack.NodaTime/MessagePack.NodaTime.csproj (nuget)
• global.json (nuget)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• 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 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.
• Raise PRs immediately (after branch is created).
• Use semantic prefixes for commit messages and PR titles.
• Use chore as semantic commit type for commit messages and PR titles.
• Separate each major version of dependencies into individual branches/PRs.
• Wait until the npm package is three days old before raising the update, this prevents npm unpublishing a package you already upgraded to.
• Automerge patch and minor upgrades if they pass tests.
• Raise a PR first before any automerging.
• Do not separate patch and minor upgrades into separate PRs for the same dependency.
• Pin dependency versions for devDependencies.
• Group all minor and patch updates together.

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

chore(deps): update all non-major dependencies

• Schedule: ["at any time"]
• Branch name: renovate/all-minor-patch
• Merge into: master
• Upgrade Microsoft.NET.Test.Sdk to 17.11.0
• Upgrade dotnet-sdk to 6.0.425

chore(deps): update actions/checkout action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: master
• Upgrade actions/checkout to v4

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

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-dotnet-4.x
• Merge into: master
• Upgrade actions/setup-dotnet to v4

chore(deps): update dependency dotnet-sdk to v8

• Schedule: ["at any time"]
• Branch name: renovate/major-8-dotnet-monorepo
• Merge into: master
• Upgrade dotnet-sdk to 8.0.401

chore(deps): update dependency microsoft.codeanalysis.netanalyzers to v8

• Schedule: ["at any time"]
• Branch name: renovate/microsoft.codeanalysis.netanalyzers-8.x
• Merge into: master
• Upgrade Microsoft.CodeAnalysis.NetAnalyzers to 8.0.0

chore(deps): update dependency microsoft.sourcelink.github to v8

• Schedule: ["at any time"]
• Branch name: renovate/microsoft.sourcelink.github-8.x
• Merge into: master
• Upgrade Microsoft.SourceLink.GitHub to 8.0.0

chore(deps): update github/codeql-action action to v3

• Schedule: ["at any time"]
• Branch name: renovate/github-codeql-action-3.x
• Merge into: master
• Upgrade github/codeql-action to v3

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