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	Ready	Preview	Jul 24, 2026 4:19pm

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

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

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

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

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