Bump LiveChartsCore.SkiaSharpView.WPF and 8 others - #4
#4Closed
dependabot[bot] wants to merge 1 commit into
masterProgressiverobot/hmailserver:masterfrom
dependabot/nuget/hmailserver/source/Tools/ControlPanel/dotnet-dependencies-8c01d866c0Progressiverobot/hmailserver:dependabot/nuget/hmailserver/source/Tools/ControlPanel/dotnet-dependencies-8c01d866c0Copy head branch name to clipboard
Closed
Bump LiveChartsCore.SkiaSharpView.WPF and 8 others#4dependabot[bot] wants to merge 1 commit intomasterProgressiverobot/hmailserver:masterfrom dependabot/nuget/hmailserver/source/Tools/ControlPanel/dotnet-dependencies-8c01d866c0Progressiverobot/hmailserver:dependabot/nuget/hmailserver/source/Tools/ControlPanel/dotnet-dependencies-8c01d866c0Copy head branch name to clipboard
dependabot[bot] wants to merge 1 commit into
masterProgressiverobot/hmailserver:masterfrom
dependabot/nuget/hmailserver/source/Tools/ControlPanel/dotnet-dependencies-8c01d866c0Progressiverobot/hmailserver:dependabot/nuget/hmailserver/source/Tools/ControlPanel/dotnet-dependencies-8c01d866c0Copy head branch name to clipboard
Conversation
Bumps LiveChartsCore.SkiaSharpView.WPF from 2.0.0-rc2 to 2.0.5 Bumps Newtonsoft.Json from 13.0.3 to 13.0.4 Bumps NLog from 5.0.1 to 6.1.3 Bumps NUnit from 3.13.3 to 4.6.1 Bumps NUnit.ConsoleRunner from 3.16.3 to 3.22.0 Bumps NUnit3TestAdapter from 4.4.2 to 6.2.0 Bumps System.Management from 8.0.0 to 10.0.9 Bumps System.ServiceProcess.ServiceController from 8.0.0 to 10.0.9 Bumps WPF-UI from 3.0.5 to 4.3.0 --- updated-dependencies: - dependency-name: LiveChartsCore.SkiaSharpView.WPF dependency-version: 2.0.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: System.Management dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet-dependencies - dependency-name: System.ServiceProcess.ServiceController dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet-dependencies - dependency-name: WPF-UI dependency-version: 4.3.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet-dependencies - dependency-name: NUnit dependency-version: 4.6.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet-dependencies - dependency-name: NUnit.ConsoleRunner dependency-version: 3.22.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: NUnit3TestAdapter dependency-version: 6.2.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet-dependencies - dependency-name: NUnit dependency-version: 4.6.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet-dependencies - dependency-name: NUnit.ConsoleRunner dependency-version: 3.22.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: Newtonsoft.Json dependency-version: 13.0.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: NLog dependency-version: 6.1.3 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
Author
|
Superseded by #5. |
dependabot
Bot
deleted the
dependabot/nuget/hmailserver/source/Tools/ControlPanel/dotnet-dependencies-8c01d866c0
branch
June 19, 2026 22:44
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 LiveChartsCore.SkiaSharpView.WPF from 2.0.0-rc2 to 2.0.5.
Release notes
Sourced from LiveChartsCore.SkiaSharpView.WPF's releases.
2.0.4
The first weeks after 2.0.0 were focused on one thing: working through the issue backlog that built up during the long
beta / rc cycle. These four patch releases bring the project to its lowest open-issue count in years — more than 40
reported issues fixed across every supported platform, with no behavioral changes to the public API shipped in 2.0.0.
If you're on 2.0.0 you can drop 2.0.4 straight in: same APIs, same defaults, just fewer bugs.
Highlights:
at least one pinned report cleared in this round.
stacked-series z-index baseline, gauge tight-bounds collapse, axis pin preserved under zoom, null-gap line rendering
on inserts/resize, mixed-sign stacking, a MinSeparators floor, granular pan/zoom flags, and runtime AnimationsSpeed
propagation.
bugs — z-order, theme inheritance, pointer-capture loss, tab/scroll mount cycles — won't regress silently.
Fixes
Core / chart engine
GeoMap
... (truncated)
2.0.0
It has been a long journey to build a charting library that works seamlessly across all .NET UI frameworks. Today, we’re excited to announce the first stable release of the library.
This release doesn’t introduce new features; instead, the focus has been entirely on stability. More than 150 new tests have been added to ensure the library remains reliable well into the future.
What’s next for the library?
There are many excellent charting libraries available, but LiveCharts was created to help developers build stunning, modern UIs. At the moment, there are no examples or showcases that truly demonstrate the library’s full potential—so that’s what’s coming next. Expect new examples that highlight what LiveCharts can really do.
What's Changed
New Contributors
Full Changelog: Live-Charts/LiveCharts2@v2.0.0-rc6...2.0.0
2.0.0-rc6
After months of deep work and iteration, this release is finally here. There is XAML and hot reload support, reworked rendering for serious performance gains, and leaned hard into source generation to clean up and future-proof the codebase. Oh, and yes: LiveCharts is now AOT-friendly. It’s faster, cleaner, and more flexible than ever.
Seamless XAML Integration via Source Generators
LiveCharts now uses a powerful source generator that automatically transforms chart objects into designer-friendly UI components. For example, the generic LineSeries now has a corresponding XamlLineSeries class—part of a new naming convention where all UI-bound types are prefixed with Xaml. These components support data bindings, themes, hot reload, and full design-time integration:
This update dramatically improves the chart design experience. You can now fully style your charts using pure XAML, including theme support—no more ViewModel hacks or SkiaSharp dependencies just to customize visuals. In previous versions, UI customization often required logic in the ViewModel, which led to tightly coupled and less maintainable code. That’s now a thing of the past.
Documentation for XAML platforms has been fully updated (thanks, Copilot!) to showcase the new syntax. While the new XAML-first approach is recommended, the legacy syntax remains supported for backward compatibility.
On non-XAML platforms, MVVM usage has been phased out from examples across the site and repo, reflecting a cleaner, more platform-native approach.
Rendering is significantly faster
The rendering pipeline has undergone a deep overhaul. LiveCharts now manages SkiaSharp resources far more efficiently, with cleaner, hardware-accelerated implementations and tight synchronization with the OS screen refresh rate. We've also added custom integrations for UI frameworks—most notably, full support for the Uno Skia renderer.
SkiaSharp shaders, paints, and text blobs are now cached wherever possible, resulting in dramatically faster rendering times, smoother animations, and reduced resource consumption across the board.
Previously, LiveCharts relied on a fixed render loop that invalidated the control every ~16ms to simulate a 60 FPS refresh rate. While functional, this approach forced redraws regardless of whether the system was ready to display them. Now, rendering is fully delegated to the OS or UI framework. For example:
This shift gives LiveCharts precise control over when and how frames are drawn—resulting in better performance and smoother visuals across platforms.
While it's hard to quantify the full performance gains (older versions lacked the benchmarking tools introduced in this release), the difference is substantial. Benchmarks in #1915 and #1936 offer a glimpse, but real-world usage shows even greater improvements.
As a bonus, there's now a "low-ish level" sample that removes the SkiaSharp dependency entirely—using Direct2D via Vortice—while still reusing 99% of the charting logic. This opens the door to even more rendering flexibility in the future.
Smarter Architecture with Source Generators
While this is an internal feature, it deserves the spotlight—because it radically simplifies how LiveCharts is built and maintained.
The library now uses a unified codebase, and a source generator automatically transforms core chart components into UI controls tailored for each supported framework. This means we write the logic once, and the generator handles the rest.
In previous versions, adding a new property to a chart control was a tedious, error-prone process. You had to manually define:
It was repetitive, fragile, and frankly exhausting.
Now? It’s magical. The generator takes care of all the boilerplate, translating properties and control logic across frameworks automatically. The result: a cleaner, more maintainable codebase—and a much more enjoyable development experience.
... (truncated)
2.0.0-rc5
This release brings a lot of improvements to the library, more than 400 commits from the last release; The library it is now compatible with net 9 on Maui, uses SkiaSharp 3 by default (when the UI framework supports it), it supports now GPU rendering (when the UI framework supports it), fixes a lot of pointer-interaction-related issues, improves events, visual elements are easier to customize, and also the drawing engine was re-structured.
Drawing engine improvements
The drawing engine in older versions was really simple, as the library evolved new features were required, like Layouts, but there was one thing missing, when an element was inside a layout, Canvas transform was not applied to the children, this is now supported and required important changes in the internal code of the library that handles drawing, this feature is now used by default on tooltips:
The opacity and scale from the tooltip geometry is also applied to the content inside the tooltip, that was missing in the library and was impossible in older versions, it is a small detail but was required.
The drawing engine code is much cleaner now, the library used interfaces to define all shapes in the core of library, for example the
IRoundedRectangleGeometry, then on the SkiaSharp assembly, there was an implementation of this interface; Now instead there is a base abstract class in the core of the library (BaseRoundedRectangleGeometry that inherits from DrawnGeometry), this base class handles animations and transforms, then on the SkiaSharp assembly, we inherit from this base class and just use SkiaSharp to draw the rectangle (see RoundedRectangleGeometry), this is much cleaner and has the potential to remove the dependency of the library on SkiaSharp.More info at #1705.
Maui Net 9 friendly
in older versions, Maui handlers were not registered following the Maui logic, this caused issues like #1684, or #1703 this is now fixed, but there are breaking changes, you must now call
.UseLiveCharts()in theMauiProgram.csfile, more info in the installation guide.New Visual elements
VisualElements felt hacky, they were hard to customize, now it is much easier to draw anything we need in the canvas, there a lot of new examples in the web site, the old Visuals are still supported but some of them are marked as obsolete.
GPU rendering
When your app starts, you can now call
LiveCharts.UseGPU = truethis will use the Hardware accelerated view provided by SkiaSharp, there are known limitations, this is not supported on NetFramework due #3111, and also not on Avalonia or Eto, where they provide the Skia assemblies.New FPS log
We can now know the frames per second on a chart by setting
LiveCharts.ShowFPS = true;and even try to get more, for exampleLiveCharts.MaxFps = 90;, the default is 65, not supported on Avalonia, where frames are handled by the framework.How many FPS can Blazor render?
About 60, not bad! but that was only the tooltip, now let's move the chart:
Still decent ❤️
Pointer interaction
There is a lot of feedback about how users try to interact with the chart, this version tries to take all that feedback and provide a solution for all the cases, the FindingStrategy property on a CartesianChart, is more flexible, this property allows the user to configure how the library selects points on the chart, the library provides 8 different strategies, but when that is not enough you also create your own logic now, more info at #1687.
The events article was also updated to explain more about this common scenario.
Axis scales
... (truncated)
2.0.0-rc4
This release is a detailed review on every open issue in the library, the reliability of the library should be drastically improved.
Now the library is compatible with SkiaSharp 3, also the Maui, Uno and WinUI views use SkiaSharp 3 by default.
There are still some issues that need attention before the first GA version.
Breaking Changes
There are no breaking changes, but this release removes most of the code that was marked as
[Obsolete]in previous versions, so before updating to this version, ensure that there is no an Obsolete warning in the compiler log, here is a list of the most common features in the library that were removed in older versions:point.PrimaryValue, now usepoint.Coordinate.PrimaryValueAsLiveChartsPieSeries()extension changed toAsPieSeries()MauiProgram.csfile, change.UseSkiaSharp(true)to.UseSkiaSharp()All the documentation on the website is updated, all obsoletes should be removed fro docs now, to get a full list please see the changes on #1625.
Highlights
Axis.LabelsDensitypropertyNew samples
The library now has advanced customization samples like:
Using Svg paths as labels:
Change the rotation of each point based on the data.
fixed issues:
... (truncated)
2.0.0-rc3.3
What's Changed
New Contributors
Full Changelog: Live-Charts/LiveCharts2@v2.0.0-rc2...v2.0.0-rc3
Commits viewable in compare view.
Updated Newtonsoft.Json from 13.0.3 to 13.0.4.
Release notes
Sourced from Newtonsoft.Json's releases.
13.0.4
Commits viewable in compare view.
Updated NLog from 5.0.1 to 6.1.3.
Release notes
Sourced from NLog's releases.
6.1.3
Improvements
6.1.2
Improvements
6.1.1
Improvements
6.1
Improvements
6.0.7
Improvements
6.0.6
Improvements
6.0.5
Improvements
6.0.4
Improvements
6.0.3
6.0.2
6.0.1
Improvements
6.0
Major changes:
ReadOnlySpanto reduce memory allocationsFlushAsyncandIDisposableAsyncConcurrentWritesArchiveSuffixFormatNLog v6 has reduced its footprint by extracting features into separate nuget-packages:
List of all NLog 6.0 Pull Requests
See also List of major changes in NLog v6 for more details.
Thanks to all contributers: @ana1250, @Pavan8374, @smnsht, @RomanSoloweow, @wadebaird, @hangy, @lavige777, @jokoyoski, @saltukkos, @nih0n, @michaelplavnik, @Aaronmsv, @ShadowDancer, @Orace, @tvogel-nid, @martinzding, @kurnakovv, @dance, @JohnVerheij
6.0.0-rc4
Improvements
6.0.0-rc3
Improvements
6.0.0-rc2
Improvements
<IsAotCompatible>ForceWriteLineReadOnlySpan<MessageTemplateParameter>6.0.0-rc1
Improvements
<Nullable>enable</Nullable>and introducedLayout.Empty[RequiredParameter]as obsolete, and replaced with explicit option validation during initialization.LogEventInfo.SequenceIDand${sequenceid}as obsolete, and instead use${counter:sequence=global}.[OverloadResolutionPriority(-1)]when using C# 13Unless something bad is discovered, then this will be the last preview build, before the final release of NLog v6.0
Updated NLog v6.0 release notes: https://nlog-project.org/2025/04/29/nlog-6-0-major-changes.html
6.0.0-preview1
Major Changes
NLog v6.0 release notes: https://nlog-project.org/2025/04/29/nlog-6-0-major-changes.html
List of all NLog 6.0 Pull Requests
Thanks to all contributers: @ana1250, @Pavan8374, @smnsht, @RomanSoloweow, @wadebaird, @hangy, @lavige777, @jokoyoski, @saltukkos, @nih0n, @michaelplavnik, @Aaronmsv, @ShadowDancer, @Orace, @tvogel-nid, @martinzding, @kurnakovv
5.5.1
5.5
Improvements
5.4
Improvements
5.3.4
Improvements
5.3.3
Improvements
5.3.2
Bug Fix
5.3.1
Improvements
5.2.8
Improvements
5.2.7
Improvements
5.2.6
Improvements
5.2.5
Improvements
5.2.4
Improvements
5.2.3
Improvements
Description has been truncated