I'm in the same situation, and have the same setup. I've set up multiple isolated environments (dev/stg/prod) in order to test/validate version migrations. I've pinned the git clone to the specific tags/V1.5 release (watch out the "V" changes case sometimes) , and generally I wait for "official" releases rather than going off of main which changes quite frequently. Dev is good for smoke tests, and staging allows me to test prisma migrations with somewhat simulated real data, before performing the same on prod. I always
pg_dump
prior to prod migrations so I can "roll back" if needed.