4 Commits

Include renames

Author	SHA1	Message	Date
implementer	3f80063303	feat: add migration advisory lock to database-postgres (E00-S03-T04)	2026-08-30 00:08:57 +00:00
implementer	7f6450410e	feat: add migration ledger to database-postgres (E00-S03-T03) ... MigrationLedger over the package-owned pg Pool: ensure() creates the schema_migrations table (version text PRIMARY KEY, applied_at timestamptz NOT NULL DEFAULT now()) with idempotent DDL; record() inserts an applied migration with a parameterized, idempotent statement (ON CONFLICT DO NOTHING — a rerun never double-applies); has()/applied() read the ledger back in apply order. Re-exported from the driver boundary (src/index.ts) so no other package needs the pg driver to touch migration state.	2026-08-29 23:19:56 +00:00
implementer	09b7a40d00	fix: pin database-postgres driver to the golden tuple (pg 8.22.0, Kysely 0.29.4) ... Review finding on PR #391: packages/database-postgres pinned pg@8.23.0 and kysely@0.29.5, but the architecture doc's golden tuple (Technology-Stack section 5.2 / section 7) pins pg@8.22.0 and Kysely@0.29.4. Reproducibility requires the exact documented versions. - packages/database-postgres/package.json: pg 8.23.0 -> 8.22.0, kysely 0.29.5 -> 0.29.4, @types/pg 8.23.1 -> 8.21.0 (no 8.22.x of @types/pg is published; 8.21.0 is the closest matching release, types for the immediately preceding pg minor) - pnpm-lock.yaml: regenerated with pnpm 11.23.0 (Node 24); the resolved pg dependency tree is unchanged apart from the driver version itself - tests/database-postgres-imports.test.mjs: exact-pin assertions updated to the corrected versions, with a comment noting the @types/pg choice	2026-08-29 11:27:29 +00:00
implementer	5c202ba21e	feat: add database-postgres driver boundary package (E00-S03-T02) ... - packages/database-postgres (@personal-blog/database-postgres): the single workspace package allowed to import the PostgreSQL driver — declares pg and kysely as exact dependencies (@types/pg for types) and its src/index.ts imports and re-exports the driver pieces (Pool, Kysely, PostgresDialect) so the isolation is real, not a placeholder - pnpm-lock.yaml: importer for packages/database-postgres plus the resolved pg/kysely dependency tree (frozen-lockfile install keeps working) - .gitea/workflows/ci.yml: new database-postgres-imports job runs tests/database-postgres-imports.test.mjs on every PR so the isolation criterion gates merges	2026-08-29 11:14:14 +00:00