Announcing Hasura 2.0.0-alpha.9

UPDATE: 2.0.0-alpha.10 is now available.

Never one to wait when product is ready, we are excited to announce the release of Hasura 2.0.0-alpha.9 fresh on the heels of alpha.8

This continues our journey towards 2.0 being fully feature stable. And, while ‘alpha’ in name, it is not alpha in quality. However, we do use this signifier to denote that it is a work in progress and invite feedback about any problems you may experience.

A Summary of Releases

As mentioned in the most recent release post, we have historically announced our releases via Discord and updates to the GitHub release page. As adoption continues to increase, we believe this is insufficient for the future.

To that end, we will begin to blog for each release (even if it is only small) so that you can track releases via blog, twitter (@HasuraHQ), Discord, and the Github Release page. In these posts, we will highlight a few specific elements of each release, but the exhaustive list of features and improvements is always in the changelog.

Overview

IMPORTANT: There was an issue with 2.0.0-alpha.8 when upgrading from 2.0.0-alpha.7. A workaround is enumerated in issue #6802.

We now support comparing columns across related tables. For example:

Consider two tables, items(id, name, stock) and shopping_cart(id, item_id, quantity) and these two tables are related via the item_id column. Now, while defining insert permission on the shopping_cart table, there can be a check to insert an item into the shopping cart only when there is enough stock present in the items table.

Conclusion

Please use the docker target hasura/graphql-engine:v2.0.0-alpha.9, try it out, let us know what works and what needs improvement. You can find us on Twitter (@HasuraHQ) and in Github. For ad-hoc conversation, feel free to join us on the Hasura Community Discord.

And, if you want to get started now with the latest stable release, check out the deployment simplicity of Hasura Cloud.