chore(scripts): remove obsolete one-shot data migrations#364
Merged
Conversation
All production tenants are now on the post-architecture-change runtime
(personal-workspace unification, conversations-to-top-level, identity-owned
files/automations, user-scoped creds), so the one-shot migration utilities
and their support libs are no longer needed.
Removes:
- scripts/migrate-{personal-workspaces,conversations-to-top-level,
user-creds-to-personal-workspace,files-to-identity,automations-to-identity,
tenant-files,usage-shape}.ts
- scripts/heal-truncated-personal-workspaces.ts
- scripts/cleanup-personal-workspace-members.ts
- scripts/lib/{migration-lock,resolve-workspace-owner,conversation-metadata}.ts
(imported only by the above; no src/ references)
- their integration/unit tests + the acquire-migration-lock fixture
- the migrate:* / heal:* / cleanup:* package.json script entries
The check-*-paths.ts CI guards that enforce the new architecture are kept.
tsc --noEmit passes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
All production tenants are now on the post-architecture-change runtime (personal-workspace unification →
ws_user_<id>, conversations moved to top-level, identity-owned files/automations, user-scoped credential migration). The one-shot migration utilities have served their purpose — ipsdi and bayze were the last pre-migration tenants and are now upgraded — so they're dead weight.What's removed
migrate-personal-workspaces,migrate-conversations-to-top-level,migrate-user-creds-to-personal-workspace,migrate-files-to-identity,migrate-automations-to-identity,migrate-tenant-files,migrate-usage-shape,heal-truncated-personal-workspaces,cleanup-personal-workspace-membersscripts/lib/{migration-lock,resolve-workspace-owner,conversation-metadata}.ts— imported only by the above (verified: zerosrc/imports)acquire-migration-lockfixturemigrate:*/heal:*/cleanup:*script entriesKept
scripts/check-*-paths.tsCI guards that enforce the new architecture (independent of the deleted libs)src//tests still mention these scripts by name; left as-is (architecture history, no code impact)Verification
bunx tsc --noEmitpasses (no dangling imports)