Skip to content

build(deps): centralize NuGet package versions - #574

Merged
erikdarlingdata merged 2 commits into
erikdarlingdata:devfrom
nmummau:feat/central-pack
Sep 29, 2026
Merged

erikdarlingdata merged 2 commits into
erikdarlingdata:devfrom
nmummau:feat/central-pack

Conversation

@nmummau

@nmummau nmummau commented Sep 26, 2026

Copy link
Copy Markdown
Contributor

Move all 34 package versions into Directory.Packages.props, preserving
existing versions and project-specific metadata.

Scope the framework reference entry to SSMS to avoid conflicting with
the installer's implicit SDK reference.

Update CI cache inputs and deployment triggers for the central file.

What does this PR do?

Centralizes all 34 NuGet package versions in Directory.Packages.props, making dependency updates easier to manage while preserving existing versions and project settings.

Limits the framework reference entry to SSMS because the installer gets that package automatically from the .NET SDK. Updates automated builds and deployments to recognize changes to the central package file.

Which component(s) does this affect?

  • Desktop App (PlanViewer.App)
  • Core Library (PlanViewer.Core)
  • CLI Tool (PlanViewer.Cli)
  • SSMS Extension (PlanViewer.Ssms)
  • Tests
  • Documentation

Also affects the Web App, PlanShare server, and shared build configuration.

How was this tested?

On Linux:

  • Release builds of the solution, PlanShare server, and SSMS installer passed with zero warnings.
  • SSMS extension package restore passed; its full Windows build was not tested.
  • Verified central package management across all eight projects and confirmed existing package versions and reference settings were
    preserved.

Tests were not run, and no plan files were tested. This change only reorganizes package configuration.

Checklist

@nmummau
nmummau changed the base branch from main to dev September 26, 2026 04:27
  Move all 34 package versions into Directory.Packages.props, preserving
  existing versions and project-specific metadata.

  Scope the framework reference entry to SSMS to avoid conflicting with
  the installer's implicit SDK reference.

  Update CI cache inputs and deployment triggers for the central file.
Resolves the conflicts with dev's 2026-09-28 package bumps.
Directory.Packages.props takes dev's versions: Avalonia, Avalonia.Desktop,
Avalonia.Fonts.Inter, Avalonia.Headless and Avalonia.Themes.Fluent 12.1.3,
Microsoft.SqlServer.TransactSql.ScriptDom 180.117.0 and coverlet.collector
10.1.0. It also adds Microsoft.AspNetCore.Mvc.Testing 10.0.12, which dev
added to the test project. Every version pinned on dev now has the same
central version, and no PackageReference keeps a Version attribute.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019tS6P95Dtzs4aeMpb1xqzX
@erikdarlingdata

Copy link
Copy Markdown
Owner

Claude posting for Erik Darling

Thanks for the PR. Dev changed package versions on 2026-09-28, after this branch was made, so the branch had three conflicts. I pushed a merge from dev (0c2fd6c) that resolves them:

  • Directory.Packages.props takes the versions that dev uses now: Avalonia, Avalonia.Desktop, Avalonia.Fonts.Inter, Avalonia.Headless and Avalonia.Themes.Fluent 12.1.3, Microsoft.SqlServer.TransactSql.ScriptDom 180.117.0, and coverlet.collector 10.1.0.
  • It adds Microsoft.AspNetCore.Mvc.Testing 10.0.12, which dev added to the test project.

I built the merged branch on Windows, including the SSMS extension with the MSBuild command from release.yml, and the SSMS installer. All builds passed with 0 warnings. Every project resolved the same packages as dev, and the VSIX contains the same files.

@erikdarlingdata
erikdarlingdata merged commit 8b88e48 into erikdarlingdata:dev Sep 29, 2026
3 checks passed
@erikdarlingdata erikdarlingdata mentioned this pull request Sep 29, 2026
2 of 8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants