fix(release): install bundle worker deps outside the root UI workspace

[rohitg00]

What

Adds --ignore-workspace to the pnpm install step in _bundle.yml so bundle workers install their own dependencies from their own lockfiles.

Why

After #650 unblocked pnpm setup, the re-dispatched bundle releases (pi/v0.1.12, opencode/v0.1.8, claude-code/v0.1.11) failed in build:bundle with ERR_MODULE_NOT_FOUND and "node_modules missing". The install log shows why:

Scope: all 13 workspace projects

pnpm install inside the worker directory walks up to the repo-root UI pnpm workspace and installs that instead, so the worker's own deps never land. The root pnpm-workspace.yaml note is explicit that Node bundle workers are self-contained projects with their own lockfiles, which is exactly what --ignore-workspace enforces. All three workers carry lockfileVersion: '9.0' lockfiles, compatible with the pinned pnpm@11.13.1.

Testing

CI-only change. The three failed tags will be re-dispatched through Release 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 12:05pm
workers-tech-spec	Ready	Preview	Jul 31, 2026 12:05pm

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 40 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: f67e89e3-e7d7-4bee-8b52-3f50d75e3af3

📥 Commits

Reviewing files that changed from the base of the PR and between 4935ba4 and c60a36c.

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