Repository navigation
Merge HEIC removal (PR #28) into main - #30
Conversation
Core now registers HEIC MIME types, detects the format including magic bytes, maps HEIC to JPEG output, and converts client-side via the vips pipeline or a canvas fallback. The heic2any/CDN module duplicated all of that and hooked a client_side_supported_mime_types filter that no longer exists. The remaining gap (core not setting the __heicUploadSupport flag that gates Safari's canvas fallback) is being addressed directly in core, so the plugin ships no HEIC handling at all.
Remove HEIC conversion module (now in WordPress 7.1 core) and set __heicUploadSupport flag
|
Warning Review limit reached
Next review available in: 11 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (9)
✨ 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
What
Brings the HEIC module removal from #28 into main.
Why
#28 was based on the
fix/71-core-integrationbranch and was merged into that branch about a minute after #27 merged it into main. As a result, the HEIC removal commits landed on the stale feature branch and never reached main -includes/heic-support.php,js/heic-support.js, andtests/Test_Heic_Support.phpare still present on main today.This PR fast-forwards those stranded commits (the #28 merge) into main. No new changes beyond what was already reviewed in #28.
Fixes the remaining half of #24.