Release 0.22.5 — screenshot capture hardening rollout#132
Conversation
…rors, CORS refcount, oversized-render guard, region crop at rasterize time Public auto-update rollout of the DOM-render screenshot hardening line (community contribution — thanks @atabisz, #130), validated end to end in the 0.22.4 install-test cycle: - Render failures now surface a real message for every error shape (Error, DOM Event, string, opaque object) — never "dom render failed: undefined". - The per-tab screenshot CORS DNR rule is refcounted, so concurrent captures of the same tab can't tear the rule down under each other's in-flight subresource fetches. - The post-render webp re-encode is bounded by the same 30s guard as the render itself, so an oversized re-encode fails fast with a diagnostic instead of hanging past the CLI timeout. Maintainer hardening on top: pages past the browser's canvas size limits (e.g. hundreds of thousands of pixels tall) used to return success with a silent 0-byte image — toDataURL() yields "data:," when the backing store fails to allocate. That is now an actionable error naming --region, --target-max-long-edge, and --scale. And --region is a real remedy there: region captures crop at rasterize time (crop-sized canvas, offset draw of the decoded SVG), so they work far past the canvas limit and skip the old full-render-then-re-encode crop step. Verified on the installed 0.22.4 pkg before this rollout: oversized page → actionable error; --region and --target-max-long-edge on the same page → valid captures; full/region/element/webp parity on normal pages; concurrent same-tab captures byte-identical across interleavings. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 42 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
1 participant
Version bump to 0.22.5 for the public auto-update rollout of the screenshot capture hardening line: real render error messages for every error shape, per-tab CORS rule refcounting for concurrent captures, a bounded webp re-encode, an actionable error for renders past the browser canvas limit (instead of a silent 0-byte success), and region captures that crop at rasterize time so --region works on very tall pages. Community contribution by @atabisz (#130) plus maintainer follow-up; validated end to end on an installed test build before this rollout. Full details in the release commit message.
🤖 Generated with Claude Code