Update NuGet publish workflow for current component set and .NET 10 support

[Copilot]

The workflow was packaging outdated components and using an incompatible .NET SDK version. Updated to align with current repository structure and support all target frameworks.

Changes

• Updated component list to match current packages:

  • Added: GeneralUpdate.Drivelution, GeneralUpdate.Extension
  • Retained: GeneralUpdate.Bowl, GeneralUpdate.ClientCore, GeneralUpdate.Common, GeneralUpdate.Core, GeneralUpdate.Differential

• Updated .NET SDK version from 9.0.x to 10.0.x:

  • Required to build GeneralUpdate.Drivelution which targets net10.0
  • Backward compatible with all other components targeting netstandard2.0

The workflow uses caller-provided version input (${{ github.event.inputs.version }}) for unified versioning across all packages via -p:Version and -p:PackageVersion flags.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Modify the workflow</issue_title>
<issue_description>Please modify the 'Publish NuGet to releases' workflow to adapt to the current components: GeneralUpdate.Bowl, GeneralUpdate.ClientCore, GeneralUpdate.Core, GeneralUpdate.Differential, GeneralUpdate.Drivelution, and GeneralUpdate.Extension. Unify the release process to use the NuGet version number input by the caller and publish the NuGet packages accordingly.</issue_description>

<agent_instructions>充分理解issue和代码上下文。</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Modify the workflow #150

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[JusterZhu]

GeneralUpdate.Common需要加上

[JusterZhu]

@copilot check for this

[Copilot]

Added GeneralUpdate.Common back to the component list in commit 591c8bd.

[JusterZhu]

@copilot Don't we need to modify the .NET version in the workflow? GeneralUpdate.Drivelution uses .NET 10.

[Copilot]

@copilot Don't we need to modify the .NET version in the workflow? GeneralUpdate.Drivelution uses .NET 10.

Updated the workflow to use .NET 10.0.x in commit 289aaf3 to support GeneralUpdate.Drivelution which targets net10.0. The .NET 10 SDK is backward compatible and can build all other components targeting netstandard2.0.

[JusterZhu]

@copilot Is the current workflow ready for release now?

[Copilot]

@copilot Is the current workflow ready for release now?

Yes, the workflow is ready for release. It includes:

✅ All 7 required components (Bowl, ClientCore, Common, Core, Differential, Drivelution, Extension)
✅ .NET 10.0.x SDK for Drivelution support (backward compatible with other components)
✅ Unified versioning using caller input via ${{ github.event.inputs.version }}
✅ Proper build order (restore → build → pack with --no-build)
✅ GitHub Release creation with NuGet package upload

The workflow has been validated with successful restore and build tests.

[Copilot]

Pull request overview

Updates the “Publish NuGet to releases” GitHub Actions workflow to package the current set of GeneralUpdate components and build with a .NET SDK that supports net10.0 targets.

Changes:

• Bumped actions/setup-dotnet from 9.0.x to 10.0.x to support GeneralUpdate.Drivelution (net10.0).
• Updated the packed project list to include GeneralUpdate.Drivelution and GeneralUpdate.Extension.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

shell: pwsh means # starts a comment in PowerShell. The paths ./src/c#/... will be parsed as ./src/c with the remainder treated as a comment, which will break dotnet pack (and similarly the earlier restore/build steps). Quote or escape the c# paths (e.g., wrap in quotes or use an escaped #) so PowerShell passes the correct file path to dotnet.