deps(nuget): Bump CommunityToolkit.Mvvm from 8.2.2 to 8.4.2#317
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
deps(nuget): Bump CommunityToolkit.Mvvm from 8.2.2 to 8.4.2#317dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Contributor
🔍 Copilot Code Review — Six-Lens Analysis
📋 Summary
📁 Changed files (0)(none) No findings — all changed files passed the six-lens review. ℹ️ About this reviewThis review applies the six-lens framework from code-review-agent.md:
Severity scale: 🔴 CRITICAL (must fix before merge) · 🟡 WARNING (should address) · 🔵 INFO (minor) |
--- updated-dependencies: - dependency-name: CommunityToolkit.Mvvm dependency-version: 8.4.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/nuget/CommunityToolkit.Mvvm-8.4.2
branch
from
53359e3 to
2ac4b05
Compare
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated CommunityToolkit.Mvvm from 8.2.2 to 8.4.2.
Release notes
Sourced from CommunityToolkit.Mvvm's releases.
8.4.2
What's Changed
Full Changelog: CommunityToolkit/dotnet@v8.4.1...v8.4.2
8.4.1
This release of the .NET Community Toolkit updates the MVVM Toolkit analyzers and source generator to Roslyn 5.0, so they can work with C# 14 out of the box. This means that
[ObservableProperty]on partial properties no longer needspreviewlanguage version 🎉What's Changed 🆕
--no-buildargument in dotnet test invokation by @echoix in Remove extra dash in--no-buildargument in dotnet test invokation CommunityToolkit/dotnet#1132[ObservableProperty]by @Sergio0694 in Fix C# language version checks for[ObservableProperty]CommunityToolkit/dotnet#1140New Contributors
--no-buildargument in dotnet test invokation CommunityToolkit/dotnet#1132Full Changelog: CommunityToolkit/dotnet@v8.4.0...v8.4.1
8.4.0
What's Changed 🆕
New Contributors
Full Changelog: CommunityToolkit/dotnet@v8.3.2...v8.4.0
8.4.0-preview3
What's Changed 🆕
New Contributors
Full Changelog: CommunityToolkit/dotnet@v8.3.2...v8.4.0-preview3
8.3.2
This hotfix release updates the build time validation for the Windows SDK projections, when using the .NET 9 SDK.
What's Changed 🆕
8.3.1
This hotfix release includes build time validation for the Windows SDK projections, to improve the developer experience.
What's Changed 🆕
8.3.0
What's Changed 🆕
New Contributors
Full Changelog: CommunityToolkit/dotnet@v8.2.2...v8.3.0
Note ℹ️
If you're consuming the MVVM Toolkit from
net8.0-windows10.0.xxxxx.0, you'll either need the latest servicing update of the .NET 8 SDK (ie. > 8.0.403), or as a temporary workaround you can manually specify the Windows SDK package version in your .csproj, as follows:Where "xxxxx" should match the Windows SDK you're targeting (in your "TargetFramework" property).
https://www.nuget.org/packages/Microsoft.Windows.SDK.NET.Ref/10.0.26100.41
https://www.nuget.org/packages/Microsoft.Windows.SDK.NET.Ref/10.0.22621.41
https://www.nuget.org/packages/Microsoft.Windows.SDK.NET.Ref/10.0.22000.41
https://www.nuget.org/packages/Microsoft.Windows.SDK.NET.Ref/10.0.20348.41
https://www.nuget.org/packages/Microsoft.Windows.SDK.NET.Ref/10.0.19041.41
https://www.nuget.org/packages/Microsoft.Windows.SDK.NET.Ref/10.0.18362.41
https://www.nuget.org/packages/Microsoft.Windows.SDK.NET.Ref/10.0.17763.41
Commits viewable in compare view.