Skip to content

Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.

fix(persistence): give the coverage migration its own revision id (#2019)

Raghav Chamadiya02d184f72a4a
diff --git a/packages/core/alembic/versions/0056_coverage_mapping_partial.py b/packages/core/alembic/versions/0060_coverage_mapping_partial.py
similarity index 92%
rename from packages/core/alembic/versions/0056_coverage_mapping_partial.py
rename to packages/core/alembic/versions/0060_coverage_mapping_partial.py
index 17c4542cc..2d24856ff 100644
--- a/packages/core/alembic/versions/0056_coverage_mapping_partial.py
+++ b/packages/core/alembic/versions/0060_coverage_mapping_partial.py
@@ -10,8 +10,8 @@ a property of the whole delete-then-insert ingest, so it lives on the table
Local SQLite stores get the column from the model via ``init_db``'s additive
schema reconciler; this migration covers the managed Postgres ones.
-Revision ID: 0056
-Revises: 0055
+Revision ID: 0060
+Revises: 0059
Create Date: 2026-08-28
"""
@@ -23,8 +23,8 @@ import sqlalchemy as sa
from alembic import op
# revision identifiers
-revision: str = "0056"
-down_revision: str | None = "0055"
+revision: str = "0060"
+down_revision: str | None = "0059"
branch_labels: str | Sequence[str] | None = None
depends_on: str | Sequence[str] | None = None