fix(ci): switch release job from WOLFSTAR_TOKEN to GITHUB_TOKEN

[RedStar071]

Root cause

The Create Release PR or Publish job fails at actions/checkout with:

fatal: could not read Username for 'https://github.com': terminal prompts disabled

The WOLFSTAR_TOKEN secret exists in the repo but the token it holds is expired/revoked/invalid. The snapshot_filter job (which uses the implicit GITHUB_TOKEN) passes cleanly, confirming the token itself is the problem.

Fix

• Remove token: ${{ secrets.WOLFSTAR_TOKEN }} from the release job's checkout step — it now uses the auto-provisioned GITHUB_TOKEN, which already has contents: write and pull-requests: write from the job-level permissions.
• Switch GITHUB_TOKEN: ${{ secrets.WOLFSTAR_TOKEN }} in changesets/action to GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} for the same reason.
• Switch GITHUB_TOKEN: ${{ github.token }} in the snapshot job (no functional change, just consistent style).

The changesets/action embeds the token in the remote URL when it pushes version commits, so no additional git credential setup is needed beyond what the job-level GITHUB_TOKEN provides.

Test plan

• Merge and verify the Create Release PR or Publish job completes without the auth error
• Confirm changesets can open/update the version PR as expected

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 788f255

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Warning

Review limit reached

@RedStar071, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 8 minutes and 20 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 903d9ca4-6c3d-4440-9a29-0297339fb959

📥 Commits

Reviewing files that changed from the base of the PR and between b567a26 and 788f255.

📒 Files selected for processing (1)

• .github/workflows/release.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-use-github-token

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.54%. Comparing base (b567a26) to head (788f255).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #53   +/-   ##
=======================================
  Coverage   49.54%   49.54%           
=======================================
  Files          49       49           
  Lines         870      870           
  Branches      200      200           
=======================================
  Hits          431      431           
  Misses        435      435           
  Partials        4        4           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.