ci: publish prereleases to named npm channels

[MuncleUscles]

Summary

• publish prerelease versions to the first prerelease identifier as the npm dist-tag
• example: v0.40.0-clarke.1 publishes as genlayer@clarke
• keeps stable releases on latest and prereleases off latest

Context

The participant-facing install command should be genlayer@clarke, not genlayer@rc2. npm trusted publishing can publish a new Clarke prerelease directly to that channel without needing a separate dist-tag mutation token.

Verification

• inspected workflow diff

[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: 344092f2-42f2-4b88-94e1-c798d6cbe489

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/prerelease-channel-dist-tag

---

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.}