v4.6.1

Bug Fixes

• @byline/cli — the Drizzle migration bundled with the installer (byline init) was stale: it predated the per-user list-view preferences work and so provisioned a schema missing the byline_admin_user_preferences table. Fresh installs scaffolded on 4.6.0 would come up without that table, breaking the list-view preferences feature. The bundled template is now regenerated from the current schema (23 tables, including byline_admin_user_preferences), so newly scaffolded apps provision the complete, up-to-date schema in one migration.

Migrations

• @byline/db-postgres — the numbered migration series (0000_ordinary_rhino + 0001_dashing_iron_patriot) was squashed into a single baseline migration, 0000_mushy_luckman, which now represents the full schema. Fresh databases are unaffected — they run the single baseline on an empty database and come up correctly.

  Existing databases that already applied the prior migration series must reconcile their Drizzle bookkeeping before running drizzle:migrate again. Because the squashed migration carries a newer journal timestamp, Drizzle will otherwise try to re-run it and fail with relation "byline_admin_permissions" already exists. The fix is to baseline: your schema is already correct, so you only record the squashed migration as applied rather than executing it —

  BEGIN;
  DELETE FROM drizzle.__drizzle_migrations;
  INSERT INTO drizzle.__drizzle_migrations (hash, created_at)
  VALUES ('83524165aa4901fba4a8c4892c7460bdab26cbe8e63d6782c01eeeed133a8aeb', 1784602547451);
  COMMIT;

  The hash is the SHA-256 of 0000_mushy_luckman.sql and created_at is its journal timestamp; after this, drizzle:migrate reports nothing to apply. Installations that had not yet applied the byline_admin_user_preferences migration should also apply packages/db-postgres/sql/0005_add-admin-user-preferences.sql first (idempotent).

All other @byline/* packages bumped to 4.6.1 in lockstep with no behavioural changes this cycle.