mirror of
https://github.com/supabase/supabase.git
synced 2026-10-13 13:19:09 +03:00
In "either condition" mode the cap is written as a separate rule pinned at `noncurrent_days: 1`, because S3 honors a version cap only alongside an age. A version beyond the cap was reported as expiring the moment it went noncurrent, while nothing would touch it until it was a day old. Also renames the fate to `expiry-due`, since removal happens on the next cleanup pass rather than at the instant the policy is met. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N3euXsz25sTybsGTcxCFfn