supabase

dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-06 09:55:06 +03:00

Files

T

Claude 56e5e40884 feat(storage): save bucket versioning and its retention policy

The bucket endpoints now accept `versioning_status`, and the lifecycle
configuration has its own PUT/GET/DELETE beside the bucket, so the
versioning section stops being form state only.

- Create sends `DISABLED`/`ENABLED`, then writes the retention policy as a
  second call, since Storage stores it separately from the bucket
- Edit derives `ENABLED`/`SUSPENDED` through `toVersioningStatusUpdate`;
  `DISABLED` is not an accepted update, so a bucket that was never
  versioned sends no versioning field at all
- Edit reads the stored policy back to prefill, rather than assuming none

`toLifecycleRules`/`fromLifecycleRules` map the form onto the API's rules.
"Both conditions" is one rule; "either condition" needs two, because S3
only honors a version cap alongside an age. The policy is only written
when one of the three fields the form owns actually changed — a blind PUT
replaces the whole configuration and would drop rules the dashboard
cannot model.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N3euXsz25sTybsGTcxCFfn

2026-10-05 15:04:12 +02:00

design-system

feat(chore): add a lint ratchet for shadcn rules (#51014 )

2026-10-02 14:13:59 +03:00

docs

feat(role): Allow eligible organizations to invite users as 'No-access' base role (#50922 )

2026-10-05 19:54:55 +07:00

fix(kb) - add topic name (#51186 )

2026-10-05 07:43:35 -05:00

learn

feat(chore): add a lint ratchet for shadcn rules (#51014 )

2026-10-02 14:13:59 +03:00