@CryogenicPlanetchecks…feat/lock-project-api-key-creation → master4 files · +160 −0review: @abir-taheerreview: @lingalarahul7review: @anshugarg15updated 3w agoAdds Liquibase migration v92 that installs a BEFORE INSERT trigger on public.project_api_keys. Any new insert is rejected with:
creation of new project_api_keys is disabled (ERRCODE
feature_not_supported)
UPDATE and DELETE are unaffected, so revocation / soft-delete flows continue to work.down.ts drops the trigger + function to re-enable inserts.To temporarily allow inserts (e.g. a controlled backfill), DROP TRIGGER trg_block_project_api_key_insert ON public.project_api_keys; inside a transaction and recreate it after.
make migrate locally against a dev Postgres and confirmed the trigger + function were created.INSERT INTO public.project_api_keys ... fails with the expected error message.UPDATE / soft-delete (deletedAt, deleted = true) still succeed.make rollback and confirmed inserts are accepted again.🤖 Generated with Claude Code
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| debby |  Ignored | May 23, 2026 9:11am |
Based on git blame analysis of 4 file(s):
| Contributor | Contribution | Files |
|---|---|---|
| Zen | 29% | 1 |
| lingalarahul7 | 18% | 1 |
| anshugarg15 | 15% | 1 |
| Himanshu Dixit | 10% | 1 |
| abir-taheer | 7% | 1 |
I recommend Zen — they edited packages/db/liquibase/changelog/changelog-root.json 2 days ago and are the top recent contributor to the DB changelogs, so they’ll have good context for the root changelog changes. Also suggest lingalarahul7 — they touched the same changelog about a month ago and can help validate the new migration’s compatibility with existing changelogs.
🤖 Based on git blame with recency weighting (recent edits count more).