Casework migrations: false no-deployment comments and a test migration list stuck at 15
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- postgresql, rust
- Domain
- databases, documentation
Research direction
Locate the file review_migration_postgres.rs and the migration 0015_unified_reviews.sql. Update the inaccurate comments about no database being deployed. Then, modify the test migration list in review_migration_postgres.rs to derive from the runtime's migration source instead of being hardcoded. Verify by running any existing migration tests to ensure the list is now complete.
Written by the indexing model from the issue text.
Description
Two stale statements in the Casework migration code:
- The comment in migration
0015_unified_reviews.sqland the doc comment onDROPPED_LEGACY_TABLESinreview_migration_postgres.rssay no database was ever deployed on the earlier schema. That is not accurate: released versions ran on it. Correct both so readers do not rely on it when changing migrations. review_migration_postgres.rskeeps its own list of migrations, which stops at 15, instead of reading the runtime's migration set. New migrations silently fall outside that test. Derive the list from the migration source of truth, or assert it is complete.
Noted on 2026-09-24 during the lifecycle audit.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 4h 26m
- Merged PRs (30d)
- 152
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from registrystack/registry-stack
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1393 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1383 ·
-
area:breg enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
registrystack/registry-stack#1380 ·
-
area:breg enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1379 ·
-
area:casework documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
registrystack/registry-stack#1369 ·
All issues in registrystack/registry-stack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
longbridge/gpui-kit#3223 ·
-
bug engine
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rocky-data/rocky#2181 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
oasisprotocol/oasis-sdk#2523 ·
-
[indexer] [QA] Add a focused test for the new NonRetryableError / assertSocketAlive() behavior. Openbot:ai-assisted component:indexer QA-roadmap status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
midnightntwrk/midnight-indexer#1557 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Luminous-Dynamics/mycelix#3069 ·