Skip to content

Dvara 1.6.0

Latest
Latest

Choose a tag to compare

View all tags
@grabdoc grabdoc released this 26 Jul 11:28
1.6.0
8c5bc14

Reference example stacks updated for Dvara 1.6.0.

Changes

  • Version bump — all Compose stacks (quick-start, multi-provider, ollama, full, with-email), the DOKS + GKE Helm recipes and their deploy.sh defaults, the jbang tooling, and the DigitalOcean recipe now pin 1.6.0. Chart: oci://ghcr.io/dvarahq/charts/dvara:1.6.0.
  • Documented the Community / Enterprise image split — undocumented here since 1.5.0 introduced it. dvara-llm-gateway and dvara-flightdeck are public; dvara-llm-gateway-ee, dvara-flightdeck-ee, dvara-mcp-gateway, and dvara-a2a-gateway are private to customers. The full stack uses all four private images, so without docker login ghcr.io it failed with a bare Error response from daemon: denied — an entitlement failure that reads like a typo. full/ now has its own README leading with the two prerequisites, and the image table in docker-compose/README.md is split public / private.
  • License key is optional, and the top-level README now says so — blank runs the free Community Edition; a DVARA- envelope unlocks Enterprise. One exception, now called out: the MCP and A2A planes are Enterprise-only with no Community tier, so the full stack does require a licence.
  • Corrected the full stack description — it has run five services since 1.3.0, when it gained the A2A plane, but the variants table still listed four and omitted dvara-a2a-gateway.

Verification

Every tag was checked to exist before being pinned — the two public images and the chart return 200 to an anonymous GHCR manifest request at 1.6.0, and the four Enterprise images return 403, which is what the documentation change above is about. All five Compose stacks validated with docker compose config against their own .env.example.

Pull with docker compose pull after copying .env.example → .env.

Changelog

1.6.0

  • Version bump — every Compose stack, Kubernetes/Helm recipe, the DigitalOcean recipe, and the jbang GKE tooling pin 1.6.0.
  • Documented the Community / Enterprise image split — full/ gains a README; the image table is split public / private.
  • Corrected the full stack description — five services, not four (dvara-a2a-gateway was missing).

1.5.0

  • Version bump — all Docker Compose stacks pin ghcr.io/dvarahq/dvara-*:1.5.0.
  • License key now optional — .env.example ships blank (DVARA_LICENSE_KEY=): blank runs Community Edition; set a DVARA- signed envelope for Enterprise.
  • Kubernetes image path fix — corrected the repository to ghcr.io/dvarahq/dvara-llm-gateway / dvara-flightdeck (removed the stray /dvara/ path segment) across the DOKS, GKE, multi-region, and single-tenant values.

1.4.0

  • Version bump 1.3.0 → 1.4.0 across all Compose stacks, Kubernetes/Helm recipes, the DigitalOcean recipe, and the jbang GKE tooling.
  • Removed stale "once cut" wording from the DOKS recipe so its pinning guidance matches the GKE recipe.

1.3.0

  • Version bump 1.2.5 → 1.3.0.
  • Added the A2A governance plane (dvara-a2a-gateway, port 8075) to the full Compose stack — it now demos all four planes (gateway + admin UI + MCP proxy + A2A proxy + PostgreSQL).

1.2.5 · 1.2.4 · 1.2.3 · 1.2.2 · 1.2.1

  • Routine version bumps — each pins all Compose stacks, Kubernetes recipes, the DigitalOcean recipe, and the jbang tooling to the matching Dvara patch release.

1.2.0

  • Version bump to 1.2.0.
  • Config hot-reload docs moved from PostgreSQL NOTIFY/LISTEN to config-version polling (dvara.config.poll-interval-ms), which is pooler-agnostic.
  • Grafana infrastructure dashboard metrics renamed to gateway_config_poller_* to match the new polling mechanism.

1.1.0

  • Version bump to 1.1.0 across the Compose stacks and Kubernetes/Helm recipes.

1.0.1

  • Bumped image pins 1.0.0 → 1.0.1 across Docker Compose, Kubernetes, and DigitalOcean examples.
  • Added the release ↔ Dvara version compatibility table to the root README.

1.0.0-GA

  • First general-availability release of the reference examples: Docker Compose stacks, cloud deploy recipes (DigitalOcean, Fly.io, Railway, Render, Kubernetes), gateway YAML configs, getting-started samples (Python/Node.js), SDK integrations, streaming demos, and observability dashboards.
Assets 2
Loading