Fix deploy workflow npm authentication for package publish

[Copilot]

The deployment workflow was failing during npm publish with ENEEDAUTH because no npm auth token was available in the publish step. This change wires npm auth into deploy.yml so publish jobs can authenticate against registry.npmjs.org.

• Root cause addressed

  • Publish packages ran without NODE_AUTH_TOKEN, so npm treated the runner as unauthenticated.

• Workflow change

  • Updated .github/workflows/deploy.yml to pass the npm secret into the publish step environment:
    • NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

• Scope

  • No build/test/release logic changed.
  • No package metadata or publish command behavior changed.

- run: pnpm run publishNpmPkg
  name: Publish packages
  env:
    NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

[Copilot]

Pull request overview

This PR fixes the Deployment GitHub Actions workflow so the Publish packages step can authenticate to registry.npmjs.org during pnpm run publishNpmPkg, resolving npm publish failures due to missing auth (ENEEDAUTH).

Changes:

• Adds NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} to the publish step environment in .github/workflows/deploy.yml.

---

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