# Dgraph 24.0.0-alpha is now available on Github and DockerHub

**URL:** <https://discuss.dgraph.io/t/dgraph-24-0-0-alpha-is-now-available-on-github-and-dockerhub/19274>\
**Category:** Announce\
**Tags:** dgraph, release\
**Created:** [April 8, 2024, 5:14pm UTC](https://discuss.dgraph.io/t/dgraph-24-0-0-alpha-is-now-available-on-github-and-dockerhub/19274 "2024-04-08T17:14:15Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![amaster507](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amaster507/32/4123_2.png) [@amaster507](https://discuss.dgraph.io/u/amaster507)\
**Post date:** [April 13, 2024, 3:47pm UTC](https://discuss.dgraph.io/t/dgraph-24-0-0-alpha-is-now-available-on-github-and-dockerhub/19274/13 "2024-04-13T15:47:19Z")

</div>

If only sets and not arrays, then Dgraph is not GraphQL compliant, just FYI.

> [@GraphQL+- -\> Spec Compliant GraphQL](https://discuss.hypermode.com/t/graphql-spec-compliant-graphql/5891/5):
>
> This has been requested before, but since we’re aiming for spec compliant GraphQL, I thought I’d put this here. Lists in Dgraph behave like an unordered set, which makes perfect sense from a graph point of view, but they do not suit all types of data. The [GraphQL spec](https://spec.graphql.org/draft/#sel-GAFdVFABABbruc) says that “lists are ordered sequences of values”, and I think we should aim for that. In DQL, if we want to use unordered lists for performance benefits, perhaps we could create a directive to guarantee order?

---

_[View the full topic](https://discuss.dgraph.io/t/dgraph-24-0-0-alpha-is-now-available-on-github-and-dockerhub/19274)._