Files
supabase/apps/studio/components/interfaces/Storage/FilesBuckets
Claude 7ed23e9c43 Fix restore action placement, model versioning-suspended as a third state
- Reverted the timeline row's Restore action back to its icon-only
  text-variant button — the ask to make Restore a default-variant
  button was about the "Back to latest" action in the version
  preview banner, not the per-row action in the Versions tab
- The version preview banner's action is now labeled Restore, styled
  as a default-variant button, and actually restores the previewed
  version as current (instead of just clearing the preview)
- Versioning can no longer be turned fully "off" on a bucket that's
  ever had it enabled — it moves to a new suspended state instead,
  matching how bucket versioning actually behaves. Suspending only
  stops new noncurrent versions from being created; nothing already
  retained is deleted, so the destructive typed-confirmation flow for
  disabling versioning is gone
- Added `hasVersioningHistory` (enabled OR suspended) alongside the
  existing `isBucketVersioned` (enabled only) and repointed every
  surface that manages or warns about retained version/trash data to
  the former, since a suspended bucket can still be sitting on plenty
  of it
- Bucket list "Versioning" column, plan-downgrade admonition, and the
  Versions tab now all reflect the three states (Enabled / Suspended /
  never enabled)

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TiUEvmC84bRsteqsWXHY2p
2026-08-06 14:11:37 +00:00
..