Steve Yegge 89be2a9d7f fix: add idempotency check to migration 028 (tombstone_closed_at) ...

Migration 028 lacked an idempotency check, causing it to fail on databases
where the migration had already been applied. The migration would attempt
to copy data from issues to issues_new, but both tables had the same CHECK
constraint, causing the insert to fail.

Added check for "status = 'tombstone'" in the table schema to detect if
the migration has already been applied and skip if so.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-26 20:57:57 -08:00

..

memory

test: add cmd/bd helper coverage and stabilize test runner

2025-12-26 17:55:51 -04:00

sqlite

fix: add idempotency check to migration 028 (tombstone_closed_at)

2025-12-26 20:57:57 -08:00

storage_test.go

feat(ready,blocked): Add --parent flag for scoping by epic/bead desce… (#743)

2025-12-25 21:11:58 -08:00

storage.go

feat(ready,blocked): Add --parent flag for scoping by epic/bead desce… (#743)

2025-12-25 21:11:58 -08:00