🗃️ feat(topic): add status and completed_at columns#13974
Closed
arvinxx wants to merge 2 commits into
Closed
Conversation
Adds nullable `status` enum (active/completed/archived) and `completed_at` timestamp columns to topics, plus supporting indexes on status and (user_id, completed_at). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #13974 +/- ##
===========================================
+ Coverage 66.78% 83.78% +16.99%
===========================================
Files 2044 539 -1505
Lines 174052 36730 -137322
Branches 17146 6073 -11073
===========================================
- Hits 116249 30774 -85475
+ Misses 57679 5832 -51847
Partials 124 124
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
status and completed_at columns
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
🐳 Database Docker Build Completed!Version: Pull ImageDownload the Docker image to your local machine: docker pull lobehub/lobehub:pr-release-db-migration-topic-status-f88444aImportant This build is for testing and validation purposes. |
Contributor
🚀 Desktop App Build Completed!Version: 📦 Release Download · 📥 Actions Artifacts Build Artifacts
Warning Note: This is a temporary build for testing purposes only. |
Member
Author
|
Superseded by #13994 which bundles topic status + tasks automation_mode migrations together. |
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.
This release includes a database schema migration for Topic lifecycle status. We are adding 2 new columns and 2 new indexes on the
topicstable so topic completion state can be tracked and queried per user.Migration overview
Previously, topics had no explicit completion state — callers had to infer status from other signals, which blocked features like completed-topic views and per-user completion timelines. This migration introduces the missing lifecycle fields so topic status and completion time are first-class, queryable data.
In practical terms, this unblocks upcoming topic-status UI and gives operators a cleaner signal for lifecycle reporting.
Added columns on
topics:status—textenum (active/completed/archived), nullable, no defaultcompleted_at—timestamp with time zone, nullableAdded indexes:
topics_status_idxon(status)topics_user_id_completed_at_idxon(user_id, completed_at)Notes for self-hosted users
statusis nullable, so existing rows remainNULLuntil written.The migration owner: @arvinxx — responsible for this database schema change, reach out for any migration-related issues.