Remove CLI npm publish from release workflow

[aaditagrawal]

Summary

• Remove the publish_cli job from the release workflow since this fork does not publish a CLI package to npm
• Update release and finalize job dependencies to no longer require publish_cli
• Remove unused id-token: write permission (was only needed for npm publishing)

Test plan

• Trigger release workflow and verify it completes without the npm publish step
• Verify the pipeline runs: preflight → build → release → finalize

Summary by CodeRabbit

• Chores
  • Optimized CI/CD release workflow configuration and streamlined deployment pipeline dependencies.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9cce3fc7-ce2e-4199-9fb4-178ff3d8c381

📥 Commits

Reviewing files that changed from the base of the PR and between 4de5477 and 872ecfa.

📒 Files selected for processing (1)

• .github/workflows/release.yml

---

📝 Walkthrough

Walkthrough

The pull request removes the npm CLI publishing job from the GitHub Actions release workflow. The publish_cli job and its associated steps are deleted, and job dependencies in the release and finalize workflows are updated to remove references to the removed job.

Changes

Cohort / File(s)	Summary
GitHub Actions Release Workflow .github/workflows/release.yml	Removed id-token write permission; deleted the entire publish_cli job for npm publishing; updated release and finalize job dependencies to exclude publish_cli.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A job removed, the workflow sleeps so tight,
One less task to publish through the night,
Simpler paths and cleaner lines we see,
The release flow dances wild and free! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: removing CLI npm publishing from the release workflow, which aligns with the primary objective of the changeset.
Description check	✅ Passed	The description provides clear context about what changed and why, covering the three main modifications. However, it deviates from the repository's template structure by using a custom 'Summary' and 'Test plan' format instead of following the required 'What Changed', 'Why', and 'Checklist' sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/remove-cli-publish

📝 Coding Plan

• Generate coding plan for human review comments

---

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