Request: enable Storage object versioning private alpha (capabilities.object_versioning) for project pyqonagrakxqjgnzaawf

[tranhatam-collab]

Summary

Please enable Storage object versioning private alpha (capabilities.object_versioning=true) for project ref pyqonagrakxqjgnzaawf (ap-southeast-1).

Why

We ship content-addressed digital downloads and fail-closed if Storage Info does not report is_versioned=true (exact version ID at purchase). This currently blocks production launch of https://sach.tranhatam.com.

Evidence (2026-10-26)

• GET /v1/projects/pyqonagrakxqjgnzaawf/config/storage → capabilities.object_versioning: false
• Upload to private STANDARD bucket books → Info is_versioned: false
• Bucket Edit UI has no versioning toggle
• PUT /storage/v1/bucket/books with versioningStatus: "ENABLED" returns 200 but does not enable versioning
• Support ticket: SU-525066

Ask

Enable the capability for this project (or point us to the correct early-access form / owner). Happy to join the private alpha and re-upload objects once is_versioned=true.

Thank you.

[tranhatam-collab]

Follow-up (2026-10-26 ~13:36 +07)

Still blocked — additional evidence:

Check	Result
Object Info is_versioned (books probe + SP-01 A5 PDF)	false (version UUID present but not versioned)
Bucket Edit UI	Public / size / MIME only — no versioning toggle
Dashboard localStorage	UI_PREVIEW_STORAGE_VERSIONING keys present; UI still gated on ConfigCat
/go/storage-object-versioning-early-access	404 (PR #51645 not live yet)
Docs object-versioning path	404
Support	SU-525066 (ack only)

Please enable capabilities.object_versioning=true for pyqonagrakxqjgnzaawf (and storageVersioningPrivateAlpha if required). Happy to re-upload once is_versioned=true.

[tranhatam-collab]

Still open — Management API re-check (2026-10-26 ~13:57 +07)

Not resolved. Accidental self-mark-as-answer was cleared. Please keep this open until capabilities.object_versioning=true.

Check	Result
GET /v1/projects/pyqonagrakxqjgnzaawf/config/storage	capabilities.object_versioning: false (session auth)
PATCH same path with {capabilities:{object_versioning:true}}	400 Unrecognized key: "capabilities"
Features present	imageTransformation / s3Protocol / purgeCache / icebergCatalog / vectorBuckets — no versioning feature key
Bucket Edit UI	Public / Restrict size / Restrict MIME only
Storage Info probe is_versioned	still false
Support	SU-525066 (auto-ack + our follow-up; no human technical reply yet)
Early-access /go/storage-object-versioning-early-access	still 404 (PR #51645 OPEN)

Ask: enable alpha for ref pyqonagrakxqjgnzaawf (Pro, ap-southeast-1). We will re-upload and verify is_versioned=true immediately after.

[tranhatam-collab]

Early-access form blocked by placeholder HubSpot GUID (2026-10-26 ~14:02 +07)

Tried the PR preview form (production /go/… still 404):

• Preview: https://zone-www-dot-com-git-evan-go-page-object-versioning-supabase.vercel.app/go/storage-object-versioning-early-access
• Submitted: email + project ref pyqonagrakxqjgnzaawf
• Result: HubSpot 404 — Form with guid '00000000-0000-0000-0000-000000000000' can't be found

Matches PR #51645 source TODO: placeholder GUID intentionally rejects until real HubSpot form is wired.

Please either:

1. Enable capabilities.object_versioning=true for pyqonagrakxqjgnzaawf via Support SU-525066, or
2. Publish the go-page with a real HubSpot GUID and confirm our submission, or
3. Point us to the correct invite owner.

We remain ready to re-upload and verify Info.is_versioned=true immediately after enable.

[tranhatam-collab]

Context: Management API incident (2026-10-26 ~14:06 +07)

status.supabase.com currently shows Elevated Mgmt API Error Rates in Multiple Regions (mitigations deploying). Our ask is unchanged and pre-dates this banner:

• capabilities.object_versioning still false for pyqonagrakxqjgnzaawf
• Early-access form HubSpot GUID still placeholder (00000000-…)
• Support SU-525066 + this discussion

No customer action available on our side beyond waiting for enablement / real early-access form. Happy to re-verify the moment capability flips.

[tranhatam-collab]

Update (2026-10-26): Preview early-access form now accepts submissions.

• URL: https://zone-www-dot-com-git-evan-go-page-object-versioning-supabase.vercel.app/go/storage-object-versioning-early-access
• Submitted: website https://sach.tranhatam.com, project ref pyqonagrakxqjgnzaawf → landed on /thank-you («Thanks for your request»)
• Production https://supabase.com/go/storage-object-versioning-early-access still 404
• Project still blocked: capabilities.object_versioning=false (Management API GET); Edit bucket UI has no versioning toggle; Support ticket SU-525066 awaiting human enablement
• Please enable object versioning private alpha on pyqonagrakxqjgnzaawf (ap-southeast-1, org IAI LLC Pro)

[tranhatam-collab]

SQL evidence: dark-launch check forces DISABLED (2026-10-26 ~14:32 +07)

Project pyqonagrakxqjgnzaawf, bucket books.

select versioning_status from storage.buckets where id = 'books';
-- → DISABLED

select conname, pg_get_constraintdef(oid)
from pg_constraint
where conrelid = 'storage.buckets'::regclass and conname ilike '%version%';

Results:

conname	def
buckets_versioning_dark_check	CHECK ((versioning_status = 'DISABLED'::text))
buckets_versioning_standard_only_check	STANDARD or DISABLED
buckets_versioning_status_check	DISABLED / ENABLED / SUSPENDED

Attempted (SQL Editor, postgres role):

update storage.buckets set versioning_status = 'ENABLED' where id = 'books';

→ ERROR 23514 violates buckets_versioning_dark_check (failing row shows ENABLED rejected).

Ask: Please remove/relax buckets_versioning_dark_check for this project (enable Storage object versioning private alpha / capabilities.object_versioning), then confirm we can set versioning_status='ENABLED' on books so Object Info returns is_versioned=true.

We will not drop the provider constraint ourselves.

[tranhatam-collab]

SQL re-probe (2026-10-26 ~14:50 +07) — still dark-launch blocked

Project pyqonagrakxqjgnzaawf, bucket books (private STANDARD).

select id, versioning_status from storage.buckets where id in ('books','covers');
-- books DISABLED · covers DISABLED

select conname, pg_get_constraintdef(oid)
from pg_constraint
where conrelid = 'storage.buckets'::regclass and conname ilike '%version%';
-- buckets_versioning_dark_check CHECK ((versioning_status = 'DISABLED'::text))  ← still present

update storage.buckets set versioning_status = 'ENABLED' where id = 'books';
-- ERROR 23514: violates check constraint "buckets_versioning_dark_check"

Also: Storage API PUT .../bucket/books with versioningStatus=ENABLED → HTTP 200, but object Info.is_versioned remains false. Feature Preview ON; Edit bucket UI has no versioning toggle.

SU-525066 follow-up #3 sent with same evidence. Please remove buckets_versioning_dark_check for this project / enable capabilities.object_versioning.

[tranhatam-collab]

SQL re-probe (2026-10-26 ~15:22 +07) — still dark-launch blocked

Project pyqonagrakxqjgnzaawf, bucket books.

books.versioning_status = DISABLED
buckets_versioning_dark_check still present
listed products = 0
matched payments = 0
Info.is_versioned = false (probe + SP-01 objects)
Edit bucket: Public / size / MIME only — no versioning toggle
Production /go/storage-object-versioning-early-access = 404

Support SU-525066 still awaiting human enablement (last Founder follow-up ~14:49). Preview early-access thank-you already submitted for this ref.

Please remove/relax buckets_versioning_dark_check / set capabilities.object_versioning=true for this project. We will re-verify is_versioned=true immediately and will not drop the provider constraint ourselves.

[tranhatam-collab]

Re-probe 2026-10-26 ~15:50 +07 — still dark-launch blocked

Project pyqonagrakxqjgnzaawf, bucket books.

SQL (Editor):

• books + covers → versioning_status = DISABLED
• buckets_versioning_dark_check still present (CHECK (versioning_status = 'DISABLED'))

Management API (dashboard session):

• GET /v1/projects/.../config/storage → capabilities.object_versioning = false
• Feature Preview STORAGE_VERSIONING localStorage = true — insufficient alone
• Edit bucket UI: Public / size / MIME only — no versioning toggle

App path:

• Storage object Info is_versioned=false (probe upload HTTP 200)
• listed products = 0 · matched payments = 0
• Production /go/storage-object-versioning-early-access = 404
• status.supabase.com: Elevated Mgmt API Error Rates (ongoing)

Support SU-525066 still awaiting human enablement (last Founder follow-up 14:49). We will not drop the provider constraint ourselves.

Please remove/relax buckets_versioning_dark_check / set capabilities.object_versioning=true for this project.

[k1ng-arthur]

Why do you believe that object versioning is supported in supabase at all? This post https://github.com/orgs/supabase/discussions/40482#discussioncomment-14973943 and docs https://supabase.com/docs/guides/storage/s3/compatibility suggest it is not possible. Do you have a source to suggest it is supported or currently in preview?

[tranhatam-collab]

@k1ng-arthur Thanks — fair challenge. Sources that object versioning exists as a dark-launched / private alpha (not generally GA):

1. Live schema on our Pro project pyqonagrakxqjgnzaawf (SQL Editor, 2026-10-26):

   • storage.buckets.versioning_status column with CHECK allowing DISABLED|ENABLED|SUSPENDED
   • Constraint buckets_versioning_dark_check = CHECK (versioning_status = 'DISABLED') — this is exactly a dark-launch gate (UPDATE ENABLED → ERROR 23514)
   • That would not exist if versioning were absent from the Storage control plane

2. Dashboard Feature Preview key UI_PREVIEW_STORAGE_VERSIONING / supabase-ui-preview-storage-versioning = true (localStorage) — UI still lacks a toggle until capability is enabled

3. Management API GET /v1/projects/{ref}/config/storage returns capabilities.object_versioning (currently false for us) — capability flag implies the feature surface

4. Product form / PR: early-access collect project ref — feat(www): collect project ref on the object versioning request form #51645 (feat(www): collect project ref on the object versioning request form). Preview thank-you page accepted our ref; production /go/storage-object-versioning-early-access still 404

5. Support ticket SU-525066 opened specifically for enabling capabilities.object_versioning on this project

S3 compatibility docs saying versioning is unsupported for the S3 API surface is consistent with “not GA / not via S3” — we are asking for the native Storage object versioning alpha, not claiming S3 ListObjectVersions works today.

If private alpha is closed / cancelled, please say so and we will stop escalating. Otherwise we still need buckets_versioning_dark_check relaxed + capabilities.object_versioning=true for books.