fix(release): take the bundle pnpm version from packageManager

[rohitg00]

What

Removes the version: 10 input from pnpm/action-setup in _bundle.yml so the pnpm version comes from the repo-root package.json packageManager field, matching ci.yml and _rust-binary.yml.

Why

Every deploy: bundle worker release currently fails in the Bundle build job:

Error: Multiple versions of pnpm specified:
  - version 10 in the GitHub Action config with the key "version"
  - version pnpm@11.13.1 in the package.json with the key "packageManager"

PR #570 bumped the root packageManager to pnpm@11.13.1 and removed the version: 10 pin from ci.yml and _rust-binary.yml, but _bundle.yml kept its pin, and pnpm/action-setup refuses to run when both are set.

Failed release runs: pi/v0.1.12, opencode/v0.1.8, claude-code/v0.1.11. The tags exist with the correct annotated messages, so Release can be re-dispatched for them once this lands.

Testing

CI-only change. The three failed tags will be re-run through the Release workflow via workflow_dispatch after merge to verify the bundle path end to end.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
workers	Ready	Preview	Jul 31, 2026 9:43am
workers-tech-spec	Ready	Preview	Jul 31, 2026 9:43am

[coderabbitai]

Warning

Review limit reached

@rohitg00, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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

How do review 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 refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4984ee09-b979-400c-aead-f1e630294233

📥 Commits

Reviewing files that changed from the base of the PR and between c6957fc and ff663ed.

📒 Files selected for processing (1)

• .github/workflows/_bundle.yml

---

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

[github-actions]

skill-check — worker

0 verified, 50 skipped (no docs/).

Layer	Result
structure	✓
vale	✓
ai	✓
render	✓

Four for four. Nicely done.