v0.8.9

Changes

• Bump hasura to 2.15.2 @elephant3 (#455)

v0.8.8

Changes

• add env vars for region and subdomain @nunopato (#352)

🧰 Maintenance

• chore: bump storage to 0.3.0 @dbarrosop (#438)

v0.8.7

Changes

🧰 Maintenance

• chore: bump nhost/functions to v0.1.8 @elephant3 (#435)
• chore: bump hasura storage @dbarrosop (#428)

v0.8.6

Changes

🧰 Maintenance

• chore: Bump hasura to v2.13.0 @nunopato (#418)
• chore: Bump hasura storage to v0.2.6 @nunopato (#418)
• chore: Bump auth to v0.15.0 @plmercereau (#406)

v0.8.5

Changes

• Bump nhost/functions to 0.1.7 (avoids infinite loop on lock file change) @elephant3 (#403)

v0.8.4

Changes

• bump nhost/functions to 0.1.6 which uses nodejs v16 @elephant3 (#397)
• update postgres image @nunopato (#390)
• Use native hasura cli on ARM arch @elephant3 (#387)

🐛 Bug Fixes

• Fix project init with --remote flag from homedir @elephant3 (#386)
• fix: Fix docker compose project generation @elephant3 (#361)

v0.8.3

Changes

• Update hasura auth to v0.13.2 @nunopato (#371)

v0.8.2

Changes

• Bump hasura auth to v0.13.1 @nunopato (#369)

🚀 Features

• feat: Use 1025 as default smtp port @elephant3 (#360)

🐛 Bug Fixes

• Bump nhost/functions to 0.1.5 @elephant3 (#344)
• fix: treat output of hasura cli correctly and honor custom binary @dbarrosop (#354)
• Fix detecting the location of .git for submodules @elephant3 (#353)

v0.8.1

Changes

• bump hasura auth version @nunopato (#338)

v0.8.0

What's Changed

• Use custom nhost/postgres image with correct roles by @nunopato in #327

Full Changelog: v0.7.10...v0.8.0

Important Notes:

• v0.8.0 should only be used with projects already running on their own Postgres instance instead of AWS RDS.
• All projects on the new setup are running PostgreSQL 14.5 - meaning you will have to delete your local DB folder and let nhost up recreate it.
• To check whether your project is running with the new Postgres instance, navigate to Settings, and if a Database section is available, it means it is.
• From now on, all new projects created on Nhost will already be running on the new Postgres offering. Existing projects will have to be migrated. An option to migrate with 1 click will be available soon.