22nd alpha release for v1.0.0

Changelog

New features

• Console now allows adding relationship across different schemas (fix #526) (#533)

Fixes

• Fixes a bug that caused migration from v1.0.0-alpha20 to v1.0.0-alpha21 to fail for Postgres user with restricted permissions. Earlier, hdb_views schema was dropped, now it is cleaned. (closes #567) (#568)
• Fixes a bug that caused a non-admin upsert query to return affected_rows: 1 and [{column: null}] instead of affected_rows: 0 and []. (fix #563) (#565)
• Fixes a bug that caused server to close websocket connections on initialisation error instead of sending he connection error message. (fix #537) (#572)

v1.0.0-alpha21

Changelog

Known issue

• 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.

New Features

• 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

• 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)

Other changes

• 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)

20th alpha release for v1.0.0

Changelog

• community: add json2graphql to tools (#454)
• server: add python based tests (#387)
• server: payload is now optional in connection_init message (close #470) (#471)
• server: dont set non-null constraint for manual object relationships (close #462)
• server: allow _is_null operator for filter/check permissions (close #456) (#477)

19th alpha release for v1.0.0

Changelog

• console: export event triggers component (#386)
• console: fix track_table pattern, error handling in run_sql (close #392) (#448)
• console: sort untracked table list alphabetically (close #421) (#449)
• console: fix add manual relationships state (close #442) (#450)
• server: dont reload schema cache for event deliveries (#453)
• server: indicate access key is set in the console context (close #426) (#447)
• server: dont retry http requests in the client (close #434) (#436)
• server: jwt claims check should be case-insensitive (fix #435) (#438)
• server: better handling for pgcrypto extension (fix #338) (#423)
• server: uri-decode database uri strings (fix #372) (#424)
• server: update checks on ci systems (close #319) (#383)
• cli: migration apply should not fail if there are no migrations (close #389) (#390)
• docs: merge docs into main repo (close #397) (#398)
• community: add community boilerplates and examples (#430)
• community: add installation manifests (#432)
• community: add jwt + auth0 todo example app (#445)
• community: add postgis specific docker-compose file (#452)

18th alpha release for v1.0.0 - bugfix for json api

Changelog

• console: add parallel tests and update dependencies (#374)
• server: returning on json queries now returns only affected row (fix #380) (#381)

17th alpha release for v1.0.0

Important

Structure of JWT claims required from the auth server has changed. This is a breaking change from the previous release. Till this release, all X-Hasura-* claims were at the top level of JWT claims JSON. With this release, they are to be moved under a key https://hasura.io/jwt/claims (or another claim name as configured by the JWT config). See docs for more info.

Changelog

• server: add custom namespace in jwt claims (close #350) (#364)
• server: make sure only events for existing triggers are fetched (#368)
• server: implement api to deliver a particular event (close #371) (#373)
• server: add jsonb boolean operators (close #369) (#376)
• console: add version check for event triggers (#361)
• console: update request payload event triggers (#358)
• console: handle non access key errors (#356)
• console ui buttons to export and import metadata, reload metadata api (close #293) (#323)

16th alpha release for v1.0.0 - Introduces Event Triggers

Changelog

New feature

This release include public preview for Event Triggers (#329). Read more here.

Important

If you're using a non-superuser with GraphQL Engine, execute the following statement as the extension is required by event trigger functionality:

-- create pgcrypto extension, required for UUID
CREATE EXTENSION IF NOT EXISTS pgcrypto;

Other changes

• server: generate a returning field in a mutation only when the select permission is defined (fix #340) (#341)
• server: allow selectively updating columns on a conflict during insert (fix #342)
• server: update catalog version to 2 (#357)
• console: fix error notification non json, auto height css (#354)

v1.0.0-alpha15

Changelog

Important

You can now select relationships of affected rows in any mutation (previously only Postgres columns were allowed). Unfortunately this might also break your current applications if you are using fragments or code generation tools. Previously, the type of returning field of a mutation response was <table_name>_no_rels, from now on it is just <table_name> which is same as the response type of a select query on a table.

Other changes

• do not allow creating permissions for admin role, fix #310 (#312)
• simpler root level select fields using primary keys (fix #304) (#306)
• add req_user_id as alias to x-hasura-user-id (fix #317) (#320)
• fix insert fails for non-admin roles on v1/query (fix #327) (#328)
• mutation return type and query type are same (close #315) (#324)
• add support for jwt authorization (close #186) (#255)
• compare only major and minor versions for cli-server (fix #331) (#332)
• update tests to use access key (close #113) (#296)

14th alpha release for v1.0.0

Changelog

• console: export as npm module (#279)
• console: import queries into graphiql from url in query params (#283)
• console: ignore case when comparing header names to detect access key (fix #286) (#287)
• console: permissions ui/ux improvements (close #205) (#295)
• server: fix upsert queries to work on non admin roles (fix #239) (#291)
• server: add default cmd to dockerfile (close #228) (#281)
• server: set header variables in subscription transaction (fix #297) (#299)
• cli: change hasuradb url format, export some migrate functions (#294)

13th alpha release for v1.0.0

Changelog

• server: accept null values for input values, closes #252 (#266)
• console: handle legacy operators in permissions builder (fix #268) (#270)
• server: returning returns [] when mutations affect no rows (fix #265) (#269)
• server: better error code when insertion check constraint fails (fix #257) (#267)
• server: respect the nullability of columns in generated schema (fix #256) (#276)