Repository navigation
Conversation
CLI benchmark (Lightweight Commands): no changes foundCommit
API calls: unchanged for all 7 commands. Binary size: 134.1 MB, unchanged. Details: timing ranges, API calls per command, slowest phasesTiming ranges
API calls per command
Slowest phasesNo command moved beyond noise, so there are no phase deltas. Comment |
There was a problem hiding this comment.
🤖 AI Review
Both independent reviews completed with no findings. Reading both changed files and the legacy imgproxy configuration confirmed that the six settings match legacy values and the integration assertion checks WebP negotiation. No additional actionable issues found. Tests were not run during adjudication.
Findings
No issues found.
Stats
Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0
Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: auto · Workflow run
This review runs once per PR. A maintainer can request another with a /ai-review comment.
## TL;DR fixes Studio on the stack missing the local S3 keys, so creating a vector bucket in Studio installs its wrapper like on the legacy backend ## ref: - extends: supabase#7483
TL;DR
fixes image transforms on the stack returning different images than the legacy backend, by giving the stack's imgproxy the same settings
what's Improved?
on the stack,
supabase startran imgproxy without the tuning the legacy backend passes ita png requested by a browser that accepts webp came back as png instead of webp
animated gifs came back as a single frame, and large photos skipped the default 3000px size cap
fixed now by:
the stack's imgproxy now gets the same tuning as the legacy backend, so transforms return the same images on both
IMGPROXY_USE_ETAGis left out because imgproxy treats its legacy value like unset, so nothing changes thereref: