Releases

Complete version history, release notes, and upgrade guides for all Geode releases.

Overview

This section documents the current stable release, the active development line, and the major release series that landed since the docs site was last synchronized. The v0.3 through v0.6 series — released between April and June 2026 — added native time-series, BM25 full-text search, and OpenTelemetry instrumentation, alongside continued transport, storage, and security hardening.

Tip
The version shown across this site is resolved automatically from the latest release tag in GitLab at build time. For the authoritative, per-tag release notes, browse the Geode tags on GitLab .

Current Release

v0.6.10 (Current Stable)

Release Date: June 1, 2026 Status: Stable release

Key Highlights:

  • First v0.6.x release to clear the full test-harness-integration suite and reach the apt deploy chain
  • Release-pipeline hardening: tag-version stamping, build-toolchain fixes, and bounded QUIC workers
  • Carries the full v0.3–v0.6 feature surface: native time-series , full-text search , and OpenTelemetry instrumentation
  • Ships as Debian packages through the official apt repository and as geodedb/geode:0.6.10 container images

See the Changelog for complete details.

Development Branch

main (unreleased)

The main branch can move ahead of v0.6.10 with fixes and features that have not yet been cut into a tagged release. Track in-flight work on the GitLab project .

Release Schedule

Geode follows a predictable release cadence:

  • Major Releases: Architectural changes and storage-format shifts
  • Minor Releases: New features and transport/security expansions
  • Patch Releases: Bug fixes, security hardening, and release validation

Version History

Note
The list below summarizes the major series. For the complete, authoritative per-version history, see the GitLab tags .

v0.6.0 – v0.6.10 (May 25 – June 1, 2026)

  • Release-pipeline and CI hardening across the v0.6.x patch line
  • v0.6.10 is the first v0.6.x release to clear the full integration test harness and reach the apt deploy chain
  • Stabilization of the time-series and full-text-search GQL surfaces introduced earlier in the line

v0.5.0 (April 29, 2026)

  • OpenTelemetry instrumentation surface — native OTLP metrics and traces (see Observability )

v0.4.0 (April 27, 2026)

  • Feature and hardening release in the v0.3–v0.5 development line

v0.3.0 (April 12, 2026)

  • First release of the v0.3 series, continuing the storage, transport, and GQL work that followed the v0.2 line

Major capabilities added since the last docs sync

  • Native time-series — the geode.ts.* GQL procedure surface for append-friendly (ts, value) series (docs )
  • Full-text search — durable, BM25-ranked fulltext indexes via CREATE INDEX ... USING fulltext and CALL geode.fts.search(...) (docs )
  • OpenTelemetry — first-party OTLP metrics and geode.query.execute traces (docs )

v0.2.12 - v0.2.15 (March 27-29, 2026)

  • gRPC parity fixes for RLS, auth rate limiting, CDC, and backup lock behavior
  • QUIC stream multiplexing and major poll-loop/accept-loop performance work
  • CTE execution, DOT output fixes, and cross-compilation hardening for 32-bit ARM
  • full-suite and unit-test hardening across the new storage path

v0.2.0 - v0.2.11 (March 26-27, 2026)

  • DSN graph binding and HELLO-time graph resolution
  • graph-storage engine integration with adapter bridge
  • TLS/CA certificate handling improvements and local CA auto-detection
  • security hardening for MFA, --graph, KMS tokens, metrics binding, and password handling

v0.1.11 - v0.1.39 (February 27-March 25, 2026)

  • auth graph storage, HMAC integrity verification, and offline auth maintenance commands
  • QUIC/TLS handshake, DNS, and shell keepalive fixes
  • per-graph storage isolation and backup/restore changes
  • ORDER BY large-result crash fix
  • DSN graph binding groundwork culminating in v0.1.39

v0.1.3 (January 2026)

  • original production-ready release
  • GQL compliance milestone
  • enterprise security, analytics, and operational baseline

Upgrading Geode

Before Upgrading

  1. Read Release Notes: Review changes, especially storage and transport changes
  2. Test in Staging: Upgrade a staging environment first
  3. Backup Data: Create a full backup before upgrading
  4. Check Compatibility: Verify client library, DSN, and certificate usage
  5. Review storage format changes: v0.1.28+ introduced per-graph storage; later releases removed the legacy monolithic path entirely

Example Docker Upgrade 

# 1. Backup
docker exec geode geode backup --output /backups/pre-upgrade.tar.gz

# 2. Pull new image
docker pull geodedb/geode:0.6.10

# 3. Stop container
docker stop geode

# 4. Start new container (data persists in volume)
docker run -d \
  -p 3141:3141 \
  -v geode-data:/var/lib/geode \
  --name geode \
  geodedb/geode:0.6.10

Always pair the current server with the latest client library releases:

ClientRecommended Version
Go0.1.21
Python0.3.20
Rust0.1.1-alpha.21
Zig0.2.10
Node.js1.0.1

See Client Libraries for installation and compatibility details.