Is hasura beta-5 to beta-6 upgrade breaking?

Problem

I’ve tried to update my Heroku’ hasura repo with beta-5 to beta-6 but a lot of inconsistency problem arise. I wanted to try the enum feature but seems i can’t 😞

What I think is the problem

New release brings breaking changes and data is inconsistent with past releases.

What I’ve tried

I’ve upload my my new dockerfile using heroku container:push web && heroku container:release web, all the process ended successfully.

But when I opened my app it crashed. Inspecting the logs says a lot of inconsistencies, like {"definition":{"role":"owner","comment":null,"permission":{"allow_aggregations":false,"columns":["stars","stars_id","target_id"],"filter":{}},"table":"stars"},"reason":"table \"stars\" does not exist","type":"select_permission"}

So it seems like hasura can’t undestand the actual database in Postgres.

The I rolled back downgrading the repo to beta-5 and all is normal.

Proposed solution

Warn users that upgrading when you have a working app to a new release is ⚠️ dangerous 🛑 and must be done by an expert or something in that line, so people don’t find breaking changes in their apps.

Also some testings upgrading a test app would be nice, so hasura team can tell if the release brings breaking changes to working apps with old release.

BTW: Good job with Hasure!

[0x777]

@Israel-Laguan Can share your schema and metadata? That’ll help us identify the issue that you are facing. Metadata can be exported from the console settings and schema as follows:

curl -H 'x-hasura-admin-secret: <admin-secret>' -d'{"opts":["-O","-x", "--schema-only", "-N" ,"hdb_catalog", "-N", "hdb_views"], "clean_output":true}' 'https://your-app-domain/v1alpha1/pg_dump'

[lexi-lambda]

The beta-6 release was not intended to have any backwards-incompatible changes, but it’s possible there’s a bug somewhere. If there is, we don’t know about it, and we haven’t managed to reproduce it, so it would be very helpful if you could share an example that reproduces the issue! It’s likely that the behavior you describe was not intentional, and we can fix it in the next release.

(In general, I would always recommend having a backup of your database when upgrading, but that is just judicious caution—we don’t intend to make breaking changes without being explicit about it.)