As @Tobbe notes, this is a known Prisma issue and it has been fixed in 2.15:
But, as of 2.13 Prisma migrate has been completely reworked such that db up and db save are no longer how migrations are managed.
If you cannot take the leap to hot-patch and use 2.15 and handle the new migration flow, downgrading to Prisma 2.11 is an option.