feat(migrations): Unify schema and data journals

[dcramer]

Junior can now run SQL schema migrations and TypeScript data migrations from
the same Drizzle journal. junior upgrade runs both kinds in order. The current
journals remain SQL-only; this adds the path for future data migrations without
bringing back the retired migration code.

For a schema change, update the owning Drizzle schema and run:

pnpm --filter @sentry/junior db:generate --name add_delivery_status

That generates a normal <tag>.sql migration and a Drizzle snapshot.

For a data migration, run:

pnpm --filter @sentry/junior db:generate:data --name backfill_delivery_status

That adds a <tag>.ts entry to the same journal:

import type { MigrationV1 } from "@sentry/junior-migrations";

const migration = {
  apiVersion: 1,
  async up(context) {
    void context;
  },
} satisfies MigrationV1;

export default migration;

Use schema migrations for tables, columns, indexes, and simple same-database
backfills. Use data migrations when the work needs application code, state,
Redis, or resumable progress. Plugin packages use the same commands with their
own package name.

The maintainer workflow is documented in
Database Migrations.
Existing databases without core Drizzle history still use the documented
0.107.1 bridge before upgrading.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
junior-docs	Building	Preview	Jul 23, 2026 3:27pm

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d1fa530. Configure here.}

[cursor]

Failed migration hash blocks edits

Medium Severity

After a TypeScript migration fails, its content hash is persisted on the ledger row. Any later edit to that still-unreleased file makes runMigrationJournal throw changed after it started, so a local fix cannot be retried without manually deleting the failed row. That conflicts with the documented rule that unreleased migration sources may still change.

Additional Locations (1)

• packages/junior-migrations/src/runner.ts#L234-L237

 

^{Reviewed by Cursor Bugbot for commit d1fa530. Configure here.}

[cursor]

Out flag ignored by generator

Low Severity

junior-migrations generate accepts --out and later reads/rewrites that folder, but the spawned drizzle-kit generate call never receives --out and only honors the config file's out. If those paths differ, Drizzle writes one journal while the wrapper inspects another, so generation fails or edits the wrong files.

 

^{Reviewed by Cursor Bugbot for commit d1fa530. Configure here.}