👷 build(db): add tasks.editor_data column for Task rich-editor round-trip#15239
👷 build(db): add tasks.editor_data column for Task rich-editor round-trip#15239sudongyuer wants to merge 1 commit into
Conversation
…trip Adds the `editor_data jsonb` column on `tasks` so the Task instruction editor can persist its Lexical state — image sizes, custom nodes, and other rich attributes that markdown drops. Required by LOBE-8967. `task_comments.editor_data` already exists on canary from the original 0095 task system migration; only `tasks` needed this. Migration: ALTER TABLE "tasks" ADD COLUMN IF NOT EXISTS "editor_data" jsonb Backwards compatible — column is nullable, existing rows unaffected. Self-hosted users: migration runs automatically on app startup. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Deployment failed with the following error: View Documentation: https://vercel.com/docs/accounts/team-members-and-roles |
There was a problem hiding this comment.
Sorry @sudongyuer, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## canary #15239 +/- ##
=========================================
Coverage 70.84% 70.84%
=========================================
Files 3160 3160
Lines 315544 315568 +24
Branches 27765 34400 +6635
=========================================
+ Hits 223554 223571 +17
- Misses 91821 91828 +7
Partials 169 169
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
Merged into #15186 — that PR now bundles both DB schema additions ( The Feature PR #15141 (LOBE-8967) now depends on #15186 instead of this PR. |
Summary
Adds the
editor_data jsonbcolumn on thetaskstable so the Task instruction editor can persist its Lexical state — image sizes, custom nodes, and other rich attributes that the markdown column drops.Required by LOBE-8967 (Task attachment / image upload support, see #15141). Split out per the project's
version-releaseskill Scenario 4: DB Schema Migration — schema changes ship in their own PR with a dedicated changelog so the cherry-pick ontomainstays clean for self-hosted users.Migration
taskstask_comments.editor_dataalready exists on canary from the original 0095 task system migration; onlytasksneeded this column.Why a separate PR
Per
.agents/skills/version-release/references/patch-release-scenarios.md§ 4, DB schema changes are released independently from feature code so the migration commit can be cherry-picked cleanly into arelease/db-migration-*branch for the canary → main release. Bundling schema with feature code would make that cherry-pick messy.Feature PR that depends on this column: #15141 (LOBE-8967 Task attachment upload). Once this merges, #15141 will rebase on canary.
Related
Test plan
bun run db:generateregenerates a clean migrationADD COLUMN IF NOT EXISTS)🤖 Generated with Claude Code