Release v2.4.2

[nmbrthirteen]

Ships the Windows fixes already merged to main. They are dormant until a tag, since users only get them through a release build.

Included

UTF-8 stdin (#67). main.py reconfigured stdout and stderr but not stdin — the stream that receives the task JSON from Node. On Windows Python falls back to cp1252, and U+201D encodes byte 0x9D, which cp1252 leaves undefined, so a title with a curly quote raised UnicodeDecodeError before the request was parsed. Fixed in the backend, in the launcher's nodeEnv() (which omitted the encoding vars that Run() set, leaving the MCP path exposed while studio was fine), and in a shared pythonEnv() for all four Node→Python spawns.

Filename sanitizing (#67). Export filenames now go through a shared safe_filename that strips path separators and characters Windows rejects, caps length, and escapes reserved device names (CON.fcpxml fails on Windows just as CON does).

Dead code removal (#66). The unpublishable npm/ package, 3.8M of unreferenced product shots, and the pre-native-CLI wrappers.

Version

package.json 2.4.1 → 2.4.2, with cli/VERSION regenerated by go generate. The release workflow refuses to build a tag that disagrees with package.json.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 41 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: bc428cc3-344a-4876-ba1c-aaeac08ee221

📥 Commits

Reviewing files that changed from the base of the PR and between 8d8877b and f5af50e.

📒 Files selected for processing (2)

• cli/VERSION
• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v2.4.2

---

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