feat(db): Product.content_policy migration (sub-project C, Phase 1) #83
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/copilot-content-policy-migration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sub-project C, Phase 1 — authors the live-DB migration for
Product.content_policy(Phase 0's canonical field, scrum4me-shared #16).What
vendor/scrum4me-sharedsubmodulee29f3cd → 9a0a0bd(only delta: PR #16 —content_policyfield + checker; verified the schema diff is exactly the 3-line addition, no other drift).prisma/schema.prismaregenerated viagen-schema.sh→ gainsProduct.content_policy Json?.prisma/migrations/20260614090411_add_product_content_policy/migration.sql— hand-authored (no local DB):ALTER TABLE "products" ADD COLUMN "content_policy" JSONB. Additive, nullable, no NOT NULL / DEFAULT (metadata-only in Postgres: no table rewrite, short catalog lock, no backfill).Deploy — 154's lane (plan Task M2)
Scrum4Me-web is the sole
migrate deployowner (mcp/workers have no migrations dir, onlyprisma generate). After merge, 154 runsprisma migrate deployon the live DB. Per the migrate-first rule this must land before any code that reads/writescontent_policy(Phase-2 mcp/web gates + Phase-3 DigiPlein seed). A pure shared-bump (checker + typings, enforcement not wired) is itself safe pre-migration.Verify
Local full-verify skipped (worktree has no
node_modules;verifyalso needsnext-env.d.ts/manual:build) — CI + 154 verify in-context. The change is a verified additive nullable column.🤖 Generated with Claude Code