Issue #101 update NuGet packages to latest stable version#102
Issue #101 update NuGet packages to latest stable version#102erikdarlingdata merged 8 commits intoerikdarlingdata:devfrom
Conversation
Release: dev → main (Feb 13 2026)
Release v1.1.0
Add auto-attach release assets workflow
Add CHANGELOG.md and release checksums
Some organizations require a vendor relationship or invoice before deploying open-source software. Added Supported ($500/yr) and Priority ($2,500/yr) tiers with links to the blog post and purchase page. No features are gated — the commercial tiers provide support, compatibility guarantees, and compliance paperwork. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…k/readme-commercial-support Add commercial support tiers to README
|
Thanks for putting this together @MisterZeus! I ran a full audit of every package bump against the codebase — here are the results. Build VerificationAll 4 projects build cleanly on the PR branch:
Notably, the 68 build warnings from issue #101 (CA2263 + CA1873) are gone with the updated packages. Package-by-Package AuditMicrosoft.Data.SqlClient (5.2.0 → 6.1.4) — Safe6.x removed .NET Standard/.NET 6 support (we target net8.0, so no issue), removed SqlVector (not used), and removed Constrained Execution Region error handling (mitigated by our existing retry logic and connection throttling). The codebase explicitly sets encryption via ScottPlot.WPF (5.0.52 → 5.1.57) — SafeThe breaking changes in this range (SKPaint → Paint API, SignalXY source changes, Multiplot refactoring, Bar plot restructuring) don't affect us — we only use DuckDB.NET (1.2.1 → 1.4.4) — Safe, actually beneficialNo breaking API changes. The upgrade brings a memory leak fix (1.3.2), improved parameter binding (1.4.1) for the Hardcodet.NotifyIcon.Wpf (1.1.0 → 2.0.1) — SafeDespite the major version bump, the namespace ( Microsoft.Extensions.* (8.0.0 → 10.0.3) — SafeThese .NET 10 extension packages are backward compatible with net8.0 targets. Standard practice for Microsoft.Extensions packages. System.Text.Json (10.0.2 → 10.0.3) — SafePatch bump, no changes of concern. SummaryAll clear. Merging today — thank you for the contribution! |
What does this PR do?
#101 this PR updates all the NuGet packages to their latest stable version.
Which component(s) does this affect?
How was this tested?
Describe the testing you've done. Include:
Checklist
dotnet build -c Debug) : a few warnings (not errors) were there, I can correct those in this PR if you like, or raise a separate PR instead.