haeaeae/silo-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(migrations): renumber trending_discover_snapshots 166 -> 167

Browse Source 
The shared dev DB already recorded version 166 (166_trending_blend_collection_type
from another branch), so the integer-version migration runner silently skipped our
166 and the table was never created — the trending section errored out empty.
167 is the next free version.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Quick
2026-05-29 10:57:57 -04:00
co-authored by Claude Opus 4.8
parent 81d1644cd7
commit ffef55283a
3 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/superpowers/specs/2026-05-29-trending-discover-persistent-snapshot-design.md
+4 -2
View File
@@ -57,8 +57,10 @@ The change cleanly separates **read** from **refresh**:
## Data model
New migration `166_trending_discover_snapshots` (next free number is 166; 165 is
the current max).
New migration `167_trending_discover_snapshots`. (Originally numbered 166, but
the shared dev DB had already recorded version 166 from another branch's
`166_trending_blend_collection_type`; the migration runner dedupes by integer
version, so 166 was silently skipped. Renumbered to 167, the next free version.)
```
trending_discover_snapshots
migrations/166_trending_discover_snapshots.down.sql → migrations/167_trending_discover_snapshots.down.sql
View File
migrations/166_trending_discover_snapshots.up.sql → migrations/167_trending_discover_snapshots.up.sql
View File