FluidCalendar v1.2.2 Potential Breaking Change

[vhsdream]

Best not to update to v1.2.2 right now, I'm testing it out and there are some issues:

1. The current update script will fail, due to a warning message during the prisma DB migration. It is forced to be an interactive prompt that you can't script around. Luckily we can npx prisma migrate deploy to just do the migration. Will submit that fix ASAP.
2. There is an interactive prompt because apparently there is some change in the DB schema and it warns of data loss if you proceed.

I went through the process manually and the app built, and there appeared to be no loss of data. My calendars and events are there, and the tasks as well.

However, I want to confirm with the dev that the message is not as critical as I feel it is. Perhaps it is just boilerplate.

[vhsdream]

And an update to this: There are different results depending on what command you run.

Running npm run prisma:migrate will give you the warning, if you consent, then yes, all of your data is gone, it's like starting from scratch.

Running npx prisma migrate deploy will not bring up any warning, and there seem to be fewer migrations, and your data remains intact.

I will find out from the developer which command is the right one.

[vhsdream]

I thought that there was something wrong with my DB but even from a fresh install of 1.2.0 or 1.2.1, updating to 1.2.2 with the current script will still fail.

I'm going to push the update that uses prisma migrate deploy rather than prisma migrate dev, which will at least allow the update to succeed.

But I still recommend reinstalling from scratch, which is what I'm going to do, since the original install used prisma migrate dev.