Fix npm publish workflow auth failure for scoped package releases

[Copilot]

The release publish workflow fails at npm publish for @sistent/mui-datatables with a 404/permission error during package upload. The publish step was relying on provenance/OIDC flow alone and did not provide npm token auth for the actual publish request.

• Workflow fix

  • Updated .github/workflows/publish-package.yml to pass NODE_AUTH_TOKEN from secrets.NPM_TOKEN in the Publish Package step.
  • Kept provenance enabled (--provenance) so attestations remain part of release publishing.

• Resulting behavior

  • Publish continues to use signed provenance metadata.
  • npm publish now has explicit registry authentication for the scoped package push.

- name: Publish Package
  env:
    NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
  run: |
    set -e
    npm publish --provenance --access public --verbose

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

Updates the npm publish GitHub Actions workflow to authenticate properly when publishing the scoped package @sistent/mui-datatables, while keeping provenance/attestations enabled.

Changes:

• Passes NODE_AUTH_TOKEN from secrets.NPM_TOKEN to the npm publish step.
• Removes a few trailing blank lines in the workflow file.

---

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