> ## Documentation Index
> Fetch the complete documentation index at: https://docs.falkordb.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> FalkorDB is a graph database that speaks the Redis protocol. Queries are issued as OpenCypher through the GRAPH.QUERY and GRAPH.RO_QUERY commands, not over Bolt or a SQL connection.
> FalkorDB implements a subset of OpenCypher with proprietary extensions. Do not assume Neo4j-only syntax or procedures are available — check /cypher/cypher-support and /cypher/known-limitations before using a clause.
> FalkorDB is the successor to RedisGraph, but they are separate products. Do not present RedisGraph commands, versions, or limitations as current FalkorDB behavior.
> Use the official clients listed in /getting-started/clients rather than generic Redis or Neo4j drivers, and prefer the language the user is already working in.
> Configuration parameters are set with GRAPH.CONFIG SET or at startup; cite the exact parameter name from /getting-started/configuration rather than inventing one.
> This site covers four products: FalkorDB (core), FalkorDB Cloud, FalkorDB Enterprise, and the GraphRAG SDK. Name which one an answer applies to, since setup and operations differ.

# Changelog

> Release notes for every published FalkorDB Enterprise version.

Each release is published to `oci://registry.falkordb.cloud/falkordb/falkordb-enterprise`.
See [Compatibility matrix](/enterprise/reference/compatibility) for the subchart versions that ship with
each release, and [Upgrade FalkorDB Enterprise](/enterprise/upgrades/enterprise) for the upgrade procedure.

<Update label="0.4.1" description="August 13, 2026" tags={["stable"]}>
  ### Added

  * Scheduling policy support for deployments. Node selectors and tolerations can be
    set per component for FalkorDB, Sentinel, and shards, from the deployment wizard
    and from the Admin Server API.
  * Administrators can reset a user's password.

  ### Changed

  * The `falkordb-browser` subchart moves from 2.0.9 to 2.4.0. It now reads
    `global.imageRegistry`, so the umbrella chart no longer overrides
    `falkordb-browser.image.repository`. Mirrored registries need
    `falkordb-browser:v2.4.0` before upgrading.
  * The `csi-s3` subchart moves from 0.43.4 to 0.43.7.

  ### Fixed

  * `csi-s3` and `csi-driver-nfs` images updated to clear reported vulnerabilities.
</Update>

<Update label="0.4.0" description="August 12, 2026" tags={["stable"]}>
  ### Breaking changes

  * First-party images and the Helm chart are published to `registry.falkordb.cloud`
    instead of `ghcr.io`. Existing image pull secrets, mirror configurations, and any
    pinned `ghcr.io` image references have to be updated. See
    [Migrate from 0.3 to 0.4](/enterprise/upgrades/migrations/0.3-to-0.4).
  * The chart no longer injects a default image registry through the installer. The
    registry comes from the chart's own `global.imageRegistry` value, so a registry
    supplied through `-f values.yaml` is no longer outranked.

  ### Added

  * Publish summary scripts for the enterprise database image.

  ### Fixed

  * Helm upgrades read the release revision correctly and wait for addon definitions
    to reconcile before continuing.
  * Admin UI: max uptime renders as a readable duration, memory metrics agree between
    tabs, and small non-zero CPU and memory percentages are no longer rounded away.
</Update>

<Update label="0.3.1" description="August 11, 2026" tags={["stable"]}>
  ### Added

  * Scripts to collect, mirror, and verify the third-party images the chart pulls, for
    air-gapped and mirrored-registry installations.

  ### Changed

  * The FalkorDB addon subchart moves from 1.7.1 to 1.7.2.
  * The `dm-sql-to-falkordb` subchart moves from 1.1.2 to 1.1.6.
</Update>

<Update label="0.3.0" description="August 10, 2026" tags={["stable"]}>
  ### Added

  * External DNS support, including per-pod DNS records and configuration from the
    standalone and sharded deployment wizards.
  * A confirmation dialog for starting and stopping a deployment.

  ### Changed

  * The FalkorDB addon subchart moves to 1.7.1.
  * User-facing terminology changed from "cluster" to "deployment".

  ### Fixed

  * Deployments stuck in `Pending` can be updated, so a failed create no longer
    strands them.
</Update>