chore(infra): delete legacy share storage by thdxr · Pull Request #57548 · anomalyco/opencode · GitHub
Skip to content

chore(infra): delete legacy share storage - #57548

Merged
thdxr merged 1 commit into
devfrom
delete-share-storage
Oct 20, 2026
Merged

thdxr merged 1 commit into
devfrom
delete-share-storage

Conversation

@thdxr

@thdxr thdxr commented Oct 20, 2026

Copy link
Copy Markdown
Member

Deletes the remaining legacy share storage.

  • Deletes the SyncServer Durable Object class (migration deletedClasses), erasing every stored share session on each stage.
  • Removes the Bucket and EnterpriseStorage R2 buckets. Both held only share data and have already been emptied.
  • Removes the now-unused SyncServer export from packages/function/src/api.ts.

The share routes were removed in #56939 and #57328.

Delete the SyncServer Durable Object class, erasing all stored share sessions, and remove the Bucket and EnterpriseStorage R2 buckets, which held share data and have been emptied.
@thdxr
thdxr merged commit f2a3414 into dev Oct 20, 2026
11 checks passed
@thdxr
thdxr deleted the delete-share-storage branch October 20, 2026 22:39

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks sound. I checked the diff and grepped the repo: nothing still refers to the Bucket / EnterpriseStorage resources, the SYNC_SERVER binding or the SyncServer class. With the binding and the class export both gone, Cloudflare can apply the deletedClasses migration. bun test in packages/function passes. I couldn't run the actual deploy without credentials.

Public API: unchanged. This is infra and worker internals only.

One thing worth confirming, not blocking: the migration is now sent on every deploy. For a brand-new personal stage, the worker never had a SyncServer class and has no v1 tag, so check that Cloudflare accepts oldTag: "v1" + deletedClasses: ["SyncServer"] there, or skip the migration when the stage has no existing tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant