31
loading...
Announcing Hasura 2.0.0-beta.2
With beta.1 available for about two weeks, and an immense amount of helpful feedback from our community, we are pleased to continue our march towards 2.0 final with the release of 2.0.0-beta.2.
Let us explain what a ‘beta’ is to Hasura.
At its simplest, when a release achieves beta it means:
This does not, by any means, mean that the value of our community is limited to alpha stages. In fact, now is the perfect time to test the beta releases and give us your feedback as we move towards the 2.0 stable release.
As mentioned in recent release posts, 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 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.
While we continue squashing final bugs in datasources (i.e. BigQuery) and the server, much of this release has been focused on console functionality. This includes:
These are, of course, just the highlights. All other fixes are included in the changelog.
Please use the docker target
hasura/graphql-engine:v2.0.0-beta.2, 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.
If you want to begin your upgrade journey with 2.0, and want to learn a bit more about how Hasura is being used in the enterprise, do feel free to contact us to set up a call with our solutions team.
For previous release announcements in the 2.x series, please review:
31