Fix publish workflow for npm OIDC trusted publishing

[Copilot]

The publish GitHub Actions job was failing during npm publish with a registry E404, despite building the package tarball correctly. The workflow's publish job was missing the environment property required for npm's OIDC trusted publisher authentication.

• Root cause

  • The publish job in .github/workflows/publish.yml lacked an environment property, so the OIDC token claims did not match the npm trusted publisher configuration, causing npm to reject the publish with E404.

• Workflow change

  • Added environment: release to the publish job so the OIDC token claims include the correct environment, allowing npm to verify the trusted publisher link and authenticate the publish request automatically — no NODE_AUTH_TOKEN or manual npm secret needed.

• Scope

  • Single-file workflow-only change in .github/workflows/publish.yml (no runtime/package logic changes).

publish:
    needs: test
    runs-on: ubuntu-latest
    environment: release
    permissions:
      contents: read
      id-token: write

Note: A GitHub environment named release must exist in the repository settings (Settings → Environments), and the npm trusted publisher configuration must use release as the environment name.

[parvardegr]

@copilot i am using the new npm trusted publisher, and i've added this repo as trusted publisher, fix the issue based on that, read the docssss

[Copilot]

@copilot i am using the new npm trusted publisher, and i've added this repo as trusted publisher, fix the issue based on that, read the docssss

Reverted the NODE_AUTH_TOKEN approach — not needed with OIDC trusted publishers. The root cause of the E404 was the missing environment property on the publish job. npm requires the OIDC token claims to include the environment name matching your trusted publisher configuration.

Added environment: release to the publish job. If you configured a different environment name in your npm trusted publisher settings, update it to match. You'll also need a GitHub environment called release in your repo settings (Settings → Environments → New environment → "release").

Commit: cc52cfa