Prepare documentation for upcoming Dgraph v25 release

[ryanfoxtyler]

We need to update and prepare the documentation for the upcoming Dgraph v25 release.

Tasks:

• Review all breaking changes and new features in v25
• Update installation and upgrade instructions
• Document new APIs, configuration options, and CLI commands
• Update examples and code snippets
• Add migration notes for users upgrading from previous versions
• Review and update release notes

Please coordinate with the Dgraph core team to ensure all technical details are accurate.

/cc @ryanfoxtyler

[linear]

HYP-3274 Prepare documentation for upcoming Dgraph v25 release

[mangalaman93]

Before I forget, I am going to list down the breaking changes here:

1. We do not support any weak keys for TLS/encryption/ACL/graphql because we have upgraded to Go 1.24 and Go 1.24 facilitates FIPS 140-3 compliance. See more here https://go.dev/doc/security/fips140

[ojaswa1942]

Hi team,
I see the docs are being overhauled. I am looking for clarity around the licensing requirements for enterprise features. It looks like some recent changes around the license have been made - can someone confirm if all features, including the enterprise features are now under APACHE and do not require requesting a license to activate?

Can we also include the updated information in the documentation, as needed?

[ryanfoxtyler]

@ojaswa1942 the licensing change will be effective with the release of v25. We're taking this chance to optimize some features for broad adoption.

[Georg97]

Hello dear Dgraph Team,

first off: this is not a bug report, so feel free to ignore this, if it not fits what you try to achive with the new docs.

this may sound stupid, but in my team we have kind of a journey on deciding on which graph database to use. After trying a bunch of options, neo4j, arango, nebula and dgraph, we kind of decided, that dgraph seems to be the right solution for now in terms of accessability, licensing and ease of setting up. Biggest downside being the learning curve.
I don't have much experience with graph databases, but I think Dgraphs DQL is significantly harder to grasp than cypher.

I am not sure if it lies in the nature of things or because neo4j had such a great interactive tutorial inside it, to show all basic cypher features. I find myself struggling to properly browse the documentation and built queries, how I want them. So currently I actually rely on different LLMs, which provide me almost working queries with correct dql keywords, which lead me to the right parts of the documentation, so I can experiment and build the queries how I need them.

For this, it would be nice to be able to have an llm.txt for the docs, or a copy button in the specific sections, so it is easier to work left and right with docs and llms.
If there would be a nicer getting started tutorial, which explains all important Dgraph (and Graph!) features in a single place, like graph traversals (= recursions), nested filtering etc. that would also be appreciated.

[ryanfoxtyler]

Hey @Georg97, thanks for sharing your concerns and totally aligned on LLMs/coding assistants simplifying the onboarding to Dgraph (and new technologies generally). A few thoughts:

1. We have an llms.txt for docs at https://docs.hypermode.com/llms.txt
2. We're seeing even better success with tools like Ref to add dynamic MCP-based search
3. Dgraph v25 Preview introduces a built-in MCP server so you can introduce your live schema and data into the context

With points 2 and 3 above, we're seeing great success with Claude 4 and GPT 4.1 in writing DQL queries/mutations and making schema updates. If you want to try Dgraph v25 Preview, it's deployed for all new Hypermode Graphs. You can get started at hypermode.com/login.