Skip to content

feat(users): add vercel_downstream_safety_identifier field #1848

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chrarnoldus merged 3 commits into from
Apr 1, 2026
Merged

feat(users): add vercel_downstream_safety_identifier field #1848

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c7acba9
feat(users): add vercel_downstream_safety_identifier field
kilo-code-bot[bot] Apr 1, 2026
5e75504
Fix
chrarnoldus Apr 1, 2026
abd85a0
Migration
chrarnoldus Apr 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions packages/db/src/migrations/0070_powerful_whizzer.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
ALTER TABLE "kilocode_users" ADD COLUMN "vercel_downstream_safety_identifier" text;--> statement-breakpoint
CREATE UNIQUE INDEX "UQ_kilocode_users_vercel_downstream_safety_identifier" ON "kilocode_users" USING btree ("vercel_downstream_safety_identifier") WHERE "kilocode_users"."vercel_downstream_safety_identifier" IS NOT NULL;
Copy link
Copy Markdown
Contributor Author

@kilo-code-bot kilo-code-bot Bot Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Unique index creation will lock writes on kilocode_users

kilocode_users is an existing populated table, and CREATE UNIQUE INDEX takes a write-blocking lock for the duration of the index build. Running this migration in production can stall inserts and updates against users until the index finishes. Use a concurrent index build strategy here instead of a plain CREATE UNIQUE INDEX.

Copy link
Copy Markdown
Contributor

@chrarnoldus chrarnoldus Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it wasn't a problem last time 🤷

Loading
Loading