chore(deps): update dotnet monorepo to v6 (major)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| Microsoft.Extensions.Caching.Memory (source) | nuget | major | 3.1.29 -> 6.0.1 |
| System.Composition.AttributedModel (source) | nuget | major | 1.4.1 -> 6.0.0 |
| System.Composition.Convention (source) | nuget | major | 1.4.1 -> 6.0.0 |
| System.Composition.Hosting (source) | nuget | major | 1.4.1 -> 6.0.0 |
| System.Composition.Runtime (source) | nuget | major | 1.4.1 -> 6.0.0 |
| System.Composition.TypedParts (source) | nuget | major | 1.4.1 -> 6.0.0 |
| System.Threading.Tasks.Dataflow (source) | nuget | major | 4.11.1 -> 6.0.0 |
| mcr.microsoft.com/dotnet/runtime-deps | stage | major | 3.1-cbl-mariner1.0 -> 6.0-cbl-mariner1.0 |
Release Notes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
- [ ] If you want to rebase/retry this PR, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:
- The detector detects more or fewer components than before
- The detector generates different parent/child graph relationships than before
- The detector generates different
devDependenciesvalues than before
If none of the above scenarios apply, feel free to ignore this comment 🙂
Verified this change manually locally.