Fix migration: skip inviteToken columns and index that already exist in production
Build and Push Docker Image / build (push) Successful in 8m49s Details

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Matt 2026-02-02 17:17:55 +01:00
parent 90e3adfab2
commit afe8a58535
1 changed files with 2 additions and 5 deletions

View File

@ -16,9 +16,7 @@ CREATE TYPE "EligibilityMethod" AS ENUM ('AUTO', 'MANUAL');
-- AlterTable
ALTER TABLE "Project" ADD COLUMN "foundedAt" TIMESTAMP(3);
-- AlterTable
ALTER TABLE "User" ADD COLUMN "inviteToken" TEXT,
ADD COLUMN "inviteTokenExpiresAt" TIMESTAMP(3);
-- AlterTable (inviteToken and inviteTokenExpiresAt already exist from previous migration)
-- CreateTable
CREATE TABLE "FilteringRule" (
@ -175,8 +173,7 @@ CREATE INDEX "AwardVote_projectId_idx" ON "AwardVote"("projectId");
-- CreateIndex
CREATE UNIQUE INDEX "AwardVote_awardId_userId_projectId_key" ON "AwardVote"("awardId", "userId", "projectId");
-- CreateIndex
CREATE UNIQUE INDEX "User_inviteToken_key" ON "User"("inviteToken");
-- CreateIndex (User_inviteToken_key already exists from previous migration)
-- AddForeignKey
ALTER TABLE "FilteringRule" ADD CONSTRAINT "FilteringRule_roundId_fkey" FOREIGN KEY ("roundId") REFERENCES "Round"("id") ON DELETE CASCADE ON UPDATE CASCADE;