ci: use npm auth token secret for package operations

[MuncleUscles]

Summary

• use the repo's NPM_AUTH_TOKEN secret for npm publish/dist-tag operations
• keep NPM_TOKEN as a fallback for compatibility

Context

The genlayer@clarke dist-tag workflow failed because NODE_AUTH_TOKEN was empty when referencing NPM_TOKEN. The repo secret present today is NPM_AUTH_TOKEN.

Verification

• listed repo/environment secret names only
• checked the failed workflow log showed empty NODE_AUTH_TOKEN

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ed1fb5a6-9895-400b-80de-0562ed325ef8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/npm-token-secret-name

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}