deps(nuget): Bump LiveChartsCore.SkiaSharpView from 2.0.0-rc6.1 to 2.0.5 - #46
Closed
dependabot[bot] wants to merge 1 commit into
Closed
deps(nuget): Bump LiveChartsCore.SkiaSharpView from 2.0.0-rc6.1 to 2.0.5#46dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: LiveChartsCore.SkiaSharpView dependency-version: 2.0.5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Owner
|
@dependabot rebase |
Contributor
Author
|
Looks like LiveChartsCore.SkiaSharpView is no longer updatable, so this is no longer needed. |
Owner
|
@dependabot rebase |
Contributor
Author
|
Looks like this PR is closed. If the branch still exists, you can re-open the PR and then use |
adsamcik
added a commit
that referenced
this pull request
Jul 18, 2026
…Event (#52) * deps(nuget): bump MessagePack, LiveChartsCore, EFCore.InMemory, TraceEvent MessagePack 3.1.4 -> 3.1.8: fixes multiple high/moderate severity advisories (GHSA-vh6j-jc39-fggf and others) flagged by NU1902/NU1903. LiveChartsCore.SkiaSharpView(.Avalonia) 2.0.0-rc6.1 -> 2.0.5: first stable release off the rc train. Microsoft.EntityFrameworkCore.InMemory 10.0.9 -> 10.0.10, Microsoft.Diagnostics.Tracing.TraceEvent 3.1.30 -> 3.2.5: patch bumps. Dependabot had opened PRs #46-#50 for these exact bumps, but closed all five itself ('no longer updatable, so this is no longer needed') when asked to rebase onto the now-fixed main - re-applying them directly here since MessagePack in particular carries real high-severity CVEs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 57e66df0-2e7f-41b5-a915-af2cdda67289 * deps(nuget): regenerate WireBound.Helper packages.lock.json WireBound.Helper.csproj isn't part of WireBound.slnx, so the solution-level 'dotnet restore' used to regenerate the other 8 lock files after the Directory.Packages.props bump never touched it, leaving it pinned to the vulnerable MessagePack 3.1.4. Restoring it directly picks up MessagePack 3.1.8 like every other project. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 57e66df0-2e7f-41b5-a915-af2cdda67289 * docs: update LiveChartsCore version references to 2.0.5 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 57e66df0-2e7f-41b5-a915-af2cdda67289 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
Pinned LiveChartsCore.SkiaSharpView at 2.0.5.
Release notes
Sourced from LiveChartsCore.SkiaSharpView'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
Commits viewable in compare view.