v1.0.0-alpha21

Changelog

If GraphQL Engine is configured to connect to Postgres with a non-superuser role, migration will fail while upgrading to v1.0.0-alpha21. See #567 for more details. If you are connecting with a user that has restricted access, we recommend that you to migrate to the next release, skipping this one.

Server supports getting JWK from an external URL. Useful when the auth provider (like Firebase) rotate the keys frequently. Check docs for detailed info. (close #465) (#527)
Server supports setting request headers for event trigger webhooks. Custom headers can be set by mentioning them directly or by setting them as environment variable and they will be sent while triggering the webhook. (Console UI changes are pending: #523) (#419)
Server supports editing the settings for an event trigger. (Console UI changes are pending: #489) (#367)

Fixes a bug that caused --project on CLI to behave inconsistently (close #552) (#557)
Server now accepts crs key to specify the Coordinate Reference System as accepted in GeoJSON 2008 spec. (closes #510) (#513)
Create extension commands in the server initialisation steps now explicitly sets the schema too. Earlier this had caused issues on Heroku Postgres and Amazon RDS. (fix #495) (#496)
Fixes some typos in the metadata command with CLI. (#493)
(Breaking) Removes s from query_execution_time in the server logs. The value should be treated as in seconds. You might have to change your log monitoring setup if you're relying on the presence of s. (close #509) (#553)
Fixes a bug that caused non-admin upsert queries to fail if the constraint name had capital letters. All constraint names are now quoted using quote_ident() in the insert trigger function definition. (fix #494) (#497)

server (test): add tests for subscription (#487)
console: take access key from redux state (#514)
console: fixes (close #406) (close #491) (#522)
console: update contributing guide and change mode hasuradb to server (close #517) (#538)