Fix publish workflow: use nuget pack for .nuspec files and push to GitHub Packages

[Copilot]

The publish GitHub Actions workflow was non-functional: it used dotnet pack on standalone .nuspec files (unsupported), had broken VERSION extraction, and the push steps were commented out entirely.

Changes

• Install NuGet CLI — Added sudo apt-get install -y nuget step; classic .nuspec packing requires the NuGet CLI, not dotnet pack
• Replace dotnet pack → nuget pack — Pack each .nuspec with version override via -Version $VERSION -NonInteractive
• Fix VERSION extraction — Replaced fragile arrTag=(${GITHUB_REF//\// }) + ${VERSION//v} (strips all v chars) with ${GITHUB_REF_NAME#v} (strips leading v only)
• Push to GitHub Packages — Registers https://nuget.pkg.github.com/dadhi/index.json as a source authenticated via GITHUB_TOKEN, then pushes all packed .nupkg files
• Push to NuGet.org — Pushes artifacts using NUGET_API_KEY repository secret with --skip-duplicate

[dadhi]

What are the steps to set the secrets such as secrets.GITHUB_TOKEN on gh? Where do I get GH token? Can you add a comment to yml describing those dtrps in focused/tech words?

[Copilot]

What are the steps to set the secrets such as secrets.GITHUB_TOKEN on gh? Where do I get GH token? Can you add a comment to yml describing those dtrps in focused/tech words?

Added inline comments to the workflow file in commit 5b97d12 explaining both secrets:

• secrets.GITHUB_TOKEN — automatically injected by GitHub Actions for every run; zero setup required. It has packages: write permission by default for public repos, so it can push to GitHub Packages without any manual steps.

• secrets.NUGET_API_KEY — needs one-time setup:

  1. Log in to https://www.nuget.org → account menu → API Keys → Create
  2. Set scope to Push, select the relevant package IDs (or use a glob like FastExpressionCompiler*)
  3. Copy the generated key
  4. In this GitHub repo: Settings → Secrets and variables → Actions → New repository secret
  5. Name it exactly NUGET_API_KEY and paste the key as the value

These steps are now documented directly in the YAML comments above the jobs section.