fix(mcp_store): add db_default to MCPServerTemplate category column

[cvolzer3]

Problem

The MCPServerTemplate.category column was added NOT NULL with a Python-only default="dev" and no Postgres-level default. Django's default= is applied at Model.__init__, so it is invisible to any path that doesn't go through the ORM: raw INSERTs, and the model-driven test schema build in setup_test_environment.py (which calls disable_migrations() and skips migrations entirely). Those paths hit a NotNullViolation on category.

Changes

Add db_default="dev" to the category field so Postgres carries a real column DEFAULT. New migration 0013 emits a single ALTER COLUMN ... SET DEFAULT 'dev' with no DROP DEFAULT follow-up. This matches the sibling scope column added in 0012, which already uses db_default.

How did you test this code?

I (the PostHog Slack app agent) could not run makemigrations or the test suite in this environment (no Django installed), so I hand-wrote migration 0013 to match exactly what makemigrations emits when db_default is added to the field's model state, and updated max_migration.txt. Please let CI run the migration and parity checks.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Raised from a Slack thread as a P2 inbox item. Invoked the /django-migrations skill, which flags exactly this cross-language NOT NULL hazard: a scalar Django default= does not create a Postgres column default, so non-ORM writers and the model-driven test schema build break. Followed its guidance to add both default= and db_default=. I chose an AlterField migration over a raw RunSQL so the migration reflects the model state and makemigrations reports no drift.

[github-actions]

Hey @cvolzer3! 👋

It looks like your git author email on this PR isn't your @posthog.com address (cvolzer3@gmail.com). Since you're on the PostHog team, it's worth pointing your local git author email at your @posthog.com address. Why it matters:

• Consistent work identity in git history — internal tooling that attributes commits to team members keys off your @posthog.com address.
• Keeps team contributions easy to tell apart from external community ones when scanning history.

You can fix it for this repo with:

git config user.email "you@posthog.com"

Or set it globally with git config --global user.email "you@posthog.com". No need to redo this PR — just a nudge for next time. 🙂

[github-actions]

Migration SQL Changes

Hey 👋, we've detected some migrations on this PR. Here's the SQL output for each migration, make sure they make sense:

products/mcp_store/backend/migrations/0013_alter_mcpservertemplate_category_db_default.py

BEGIN;
--
-- Alter field category on mcpservertemplate
--
ALTER TABLE "mcp_store_mcpservertemplate" ALTER COLUMN "category" SET DEFAULT 'dev';
COMMIT;

Last updated: 2026-07-13 17:53 UTC (dcf9eb0)

[github-actions]

🔍 Migration Risk Analysis

We've analyzed your migrations for potential risks.

Summary: 0 Safe | 1 Needs Review | 0 Blocked

⚠️ Needs Review

May have performance impact

mcp_store.0013_alter_mcpservertemplate_category_db_default
  └─ #1 ⚠️ AlterField
     Field alteration may cause table locks or data loss (check if changing type or constraints)
     model: mcpservertemplate, field: category, field_type: CharField

Last updated: 2026-07-13 17:53 UTC (dcf9eb0)

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[greptile-apps]

_{Reviews (1): Last reviewed commit: "fix(mcp_store): add db_default to MCPSer..." | Re-trigger Greptile}

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-07-13 18:41 UTC	Run
prod-us	✅ Deployed	2026-07-13 18:55 UTC	Run
prod-eu	✅ Deployed	2026-07-13 19:02 UTC	Run