Eldric Docs 5.0.134 ← eldric.ai
Operations

Release notes

Operations · Release notes · Applies to 5.0.134

Eldric 5.0 is the current platform line. Patch releases ship regularly; the current build is always the one published as *-latest on repo.eldric.ai, which is what dnf installs and updates to. This page summarizes what the 5.0 line delivers and what to check before you install or update.

On this pageWhat 5.0 deliversThe 5.0.x lineBefore updating

What Eldric 5.0 delivers

Eldric 5.0 runs as a single platform you install and operate on your own infrastructure. Available in the current line:

  • One package you install with dnf (CPU), plus an optional CUDA build for GPU hosts, an ARM64 minimal build and a macOS package — all from repo.eldric.ai.
  • Multi-node clustering with role-based nodes, load-balanced routing and controller high-availability.
  • An OpenAI-compatible public API through the Edge, secured with API keys — see the API reference.
  • Retrieval-augmented generation with on-device embeddings and per-tenant knowledge bases — see Using RAG.
  • Multi-agent orchestration and multi-tenant isolation.
  • A unified registry of scientific data sources, plus speech-to-text / text-to-speech, messaging and IoT capabilities.
  • Native GGUF inference without an external runtime.

The 5.0.x update line

The 5.0.x line ships stability, security and bug-fix updates on top of GA, plus incremental capabilities delivered as patches — including controller high-availability, multi-site federation and opt-in smart-memory inference. The latest packages are always published as *-latest on repo.eldric.ai; update with dnf.

CPU and GPU are separate channels

The CPU package and the CUDA package for GPU hosts are built and published independently, so they are not always at the same patch version. A mixed cluster can legitimately be running one version on its CPU nodes and another on its GPU nodes, and dnf update on each host gives you whatever is current for that package — not a single cluster-wide version.

Check what each channel currently offers before assuming they match:

dnf --showduplicates list eldric-aios
dnf --showduplicates list eldric-aios-cuda

If you need both at a specific version, pin the version explicitly rather than relying on *-latest to line up. Every node also reports its own running version at /health, which is the honest answer for a given host.

Before updating

  1. Read Known issues for current rough areas and preview features.
  2. Confirm package availability for your platform on repo.eldric.ai.
  3. Test critical API calls against a staging tenant.
  4. Back up tenant and knowledge-base state using supported workflows.
Known issuesDocumentation