wasp db upgrade issues
Backend
I recently updated some stuff on my mac (including macos to a newer version of sequioa, and somehow something got triggered to update the postgres image (18), or the registry got updated so it pulled in the newer version of postgres. I'm on wasp 19, and I still got the error described here: https://github.com/wasp-lang/wasp/issues/3321
which was supposedly fixed in wasp 0.18.2. I ended up clearing my db and doing another migrate-dev, but my production db is on postgres 17, so I'd like to keep my dev on 17 as well. Is that possible without an awkward workaround?
which was supposedly fixed in wasp 0.18.2. I ended up clearing my db and doing another migrate-dev, but my production db is on postgres 17, so I'd like to keep my dev on 17 as well. Is that possible without an awkward workaround?
GitHub
Reproduction Wasp version: 0.18.1 (latest at the time of writing) Reproduction steps: # Force Docker to fetch PG 18 docker image rm postgres:latest # Create a new app cd /tmp wasp new saas-app -t s...
