Parent
Milestone #3 — Blob migration follow-up: cutover and cleanup
What to build
Delete the ocobo-blob store from the personal "wab" Vercel account once production is confirmed green on the new website-blob store. HITL — manual action in the Vercel dashboard.
Wait at least one full deployment cycle (24 h+) after #196 lands to allow any latent reference to surface. Smoke-test everything once more before pressing delete.
Steps:
- Confirm production has been green on new store for at least one deployment cycle.
- Vercel dashboard → "wab" personal account → Storage →
ocobo-blob → Delete Store.
- Remove the old
BLOB_READ_WRITE_TOKEN value from posts/.env.local (and clean up NEW_BLOB_READ_WRITE_TOKEN if it was kept dual, renaming the new one to the canonical BLOB_READ_WRITE_TOKEN).
- Confirm no environment variable in either Vercel project still references the old store's token.
Acceptance criteria
Blocked by
Parent
Milestone #3 — Blob migration follow-up: cutover and cleanup
What to build
Delete the
ocobo-blobstore from the personal "wab" Vercel account once production is confirmed green on the newwebsite-blobstore. HITL — manual action in the Vercel dashboard.Wait at least one full deployment cycle (24 h+) after #196 lands to allow any latent reference to surface. Smoke-test everything once more before pressing delete.
Steps:
ocobo-blob→ Delete Store.BLOB_READ_WRITE_TOKENvalue fromposts/.env.local(and clean upNEW_BLOB_READ_WRITE_TOKENif it was kept dual, renaming the new one to the canonicalBLOB_READ_WRITE_TOKEN).Acceptance criteria
ocobo-blobdeleted from "wab" personal accountBLOB_READ_WRITE_TOKENvalue removed fromposts/.env.localBLOB_READ_WRITE_TOKENif it was dual-named)Blocked by