revert(mothership): back out v0.8 (#5410) and its bug fixes (#5735) from staging#5739
Closed
Sg312 wants to merge 3 commits into
Closed
revert(mothership): back out v0.8 (#5410) and its bug fixes (#5735) from staging#5739Sg312 wants to merge 3 commits into
Sg312 wants to merge 3 commits into
Conversation
This reverts commit caa454a. v0.8 is preserved on dev and will return via a future dev -> staging promotion.
This reverts commit f03b433 while keeping the 21 unrelated commits that landed on top of it (replayed onto the pre-v0.8 base to resolve the overlaps). DB bookkeeping: drizzle migration 0262_strong_storm (workspace_files.message_id) leaves the tree and its _journal.json entry is removed, so it can never run in prod. 0263_workflow_fork_sync_excluded (from the kept forking commit) is untouched - the journal goes 0261 -> 0263, which the runtime migrator orders by timestamp, matching what the staging DB already applied. v0.8 is preserved on dev.
Contributor
|
Too many files changed for review. ( Bypass the limit by tagging |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
the
requires-mothership-merge
|
The message_id migration already ran against the DB in every env, so the column exists everywhere regardless of this revert. Restore the migration file, its snapshot, the journal entry, and the schema.ts column declaration so the tree matches the DB and the recorded migration history; the revert keeps out only the v0.8 code. packages/db is now byte-identical to staging.
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
2 participants
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.
Summary
Backs mothership v0.8 out of the sim staging release line, mirroring simstudioai/mothership#358. Two revert commits undo
caa454ae(v0.8 bug fixes, #5735) andf03b4337(v0.8, #5410). The 21 unrelated commits that landed on top of v0.8 are kept: the second revert's tree was built by replaying them onto the pre-v0.8 base, so the final tree differs from staging only in paths the two reverted commits touched (verified, 0 stray paths). Everything reverted is preserved ondevand returns via a normaldev -> stagingpromotion once ready.DB bookkeeping: the
0262_strong_stormmigration (workspace_files.message_id) already ran against the DB in every env, so a follow-up commit keeps its migration file, snapshot, journal entry, and theschema.tscolumn declaration —packages/dbis byte-identical to staging. Only the v0.8 code is reverted; the migration history stays exactly as the DB recorded it (0261 -> 0262 -> 0263).Type of Change
Testing
caa454ae's diffbun install --frozen-lockfileandbun run type-checkpass on the result (thedocsapp type-check failure is pre-existing on staging —apps/docsis untouched by this PR)maincontains neither reverted commitChecklist
Companion PR
Companion: https://github.com/simstudioai/mothership/pull/358