chore: upgrade hasura to v2

[johnrees]

https://hasura.io/docs/latest/graphql/core/guides/upgrade-hasura-v2.html#migrate-hasura-v1-instance-to-hasura-v2

in theory it should just work™

there's one thing I want to check, as I think we might be using it, or might've done in the past -

Semantics of explicit “null” values in “where” filters have changed

According to the discussion in this GitHub issue, an explicit null value in a comparison input object will be treated as an error rather than resulting in the expression being evaluated to True.

For example: The mutation delete_users(where: {id: {_eq: $userId}}) { name } will yield an error if $userId is null instead of deleting all users.

The older behaviour can be preserved by setting the HASURA_GRAPHQL_V1_BOOLEAN_NULL_COLLAPSE env var to true.

[github-actions]

Removed vultr server and associated DNS entries

[DafyddLlyr]

Works for me - good find on the health check ✅

Following on from our conversation the other day, about the collapsing null - I've been using a version with this change in it for a while and haven't hit any issues with it (that I'm aware of).

@jessicamcinchak mentioned that this behaviour was present in an AddressBase related call I believe (?) which has now been removed. Is this something we're able to verify on Github to put minds at ease?

[johnrees]

Works for me - good find on the health check ✅

thanks for looking @DafyddLlyr

I did a quick scan through the repo for query: gql and I don't think there's anything there that is predicated on null dropping the filter. I'll run some more quick tests today but hopefully this one is good to go 🚀

[DafyddLlyr]

I did a quick scan through the repo for query: gql and I don't think there's anything there that is predicated on null dropping the filter. I'll run some more quick tests today but hopefully this one is good to go 🚀

Yeah I did the same and didn't see anything that could cause us issues 👍