release: v0.30.2 — Docker Hub migration (evoapicloud namespace)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: DavidsonGomes

CHANGELOG.md

@@ -5,6 +5,18 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.30.2] - 2026-04-23
+
+Patch release focused on CI/distribution: Docker images now ship from the official `evoapicloud` namespace on Docker Hub (public, no auth required on Swarm managers), and the legacy dashboard-only workflow was removed to unblock the build pipeline.
+
+### Changed
+
+- **Docker images published to Docker Hub under `evoapicloud/`** — the Swarm workflow (`.github/workflows/docker-publish.yml`) now pushes `evo-nexus-runtime` and `evo-nexus-dashboard` to `docker.io/evoapicloud/*` instead of `ghcr.io`. Requires `DOCKERHUB_USERNAME` + `DOCKERHUB_TOKEN` secrets on the repo. The `evonexus.stack.yml` template and `README.swarm.md` were updated to reference the public images — no `OWNER` placeholder to fill in, no `docker login` needed on Swarm managers.
+
+### Removed
+
+- **Redundant `dashboard.yml` workflow** — deleted `.github/workflows/dashboard.yml`, which built a Python+React-only dashboard image (`Dockerfile.dashboard`) that nothing consumes. The Swarm workflow already produces a strict superset (with terminal-server and both CLIs). This also fixes the build failure on `main` caused by a TypeScript peer-dep conflict in the legacy Dockerfile.
+
 ## [0.30.1] - 2026-04-23
 
 Patch release focused on thread UX polish: session now swaps cleanly when switching threads via the sidebar, the agent is briefed explicitly about running inside a persistent thread (not a fresh one-shot session), the assignee dropdown stops hiding agents, and fresh installs no longer inherit Evolution-specific goal seed data.

cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evoapi/evo-nexus",
-  "version": "0.30.1",
+  "version": "0.30.2",
   "description": "Unofficial open source toolkit for Claude Code — AI-powered business operating system",
   "keywords": [
     "claude-code",

docs/guides/updating.md

@@ -35,9 +35,30 @@ kill $(lsof -ti :8080) 2>/dev/null
 python app.py &
 ```
 
-## Update via Docker
+## Update via Docker (published images)
 
-If you're running EvoNexus with Docker Compose:
+Starting with **v0.30.2**, official images are published to Docker Hub under the `evoapicloud` namespace:
+
+- `evoapicloud/evo-nexus-dashboard` — Flask + React + embedded terminal + Claude CLI
+- `evoapicloud/evo-nexus-runtime` — Node/Python runtime for the Telegram bot and the scheduler
+
+The images are public — no `docker login` required.
+
+### Docker Swarm / Portainer
+
+Bump the image tag in your stack (or leave `:latest` and force a redeploy). Example:
+
+```bash
+docker service update --image evoapicloud/evo-nexus-dashboard:v0.30.2 evonexus_evonexus_dashboard
+docker service update --image evoapicloud/evo-nexus-runtime:v0.30.2   evonexus_evonexus_telegram
+docker service update --image evoapicloud/evo-nexus-runtime:v0.30.2   evonexus_evonexus_scheduler
+```
+
+See [`README.swarm.md`](https://github.com/EvolutionAPI/evo-nexus/blob/main/README.swarm.md) for the full Swarm / Portainer deployment guide and the `evonexus.stack.yml` template.
+
+### Local docker compose (building from source)
+
+If you're running `docker-compose.yml` locally (building the image from source instead of pulling from Docker Hub):
 
 ```bash
 cd /path/to/your/workspace

docs/llms-full.txt

@@ -3959,9 +3959,30 @@ kill $(lsof -ti :8080) 2>/dev/null
 python app.py &
 ```
 
-## Update via Docker
+## Update via Docker (published images)
 
-If you're running EvoNexus with Docker Compose:
+Starting with **v0.30.2**, official images are published to Docker Hub under the `evoapicloud` namespace:
+
+- `evoapicloud/evo-nexus-dashboard` — Flask + React + embedded terminal + Claude CLI
+- `evoapicloud/evo-nexus-runtime` — Node/Python runtime for the Telegram bot and the scheduler
+
+The images are public — no `docker login` required.
+
+### Docker Swarm / Portainer
+
+Bump the image tag in your stack (or leave `:latest` and force a redeploy). Example:
+
+```bash
+docker service update --image evoapicloud/evo-nexus-dashboard:v0.30.2 evonexus_evonexus_dashboard
+docker service update --image evoapicloud/evo-nexus-runtime:v0.30.2   evonexus_evonexus_telegram
+docker service update --image evoapicloud/evo-nexus-runtime:v0.30.2   evonexus_evonexus_scheduler
+```
+
+See [`README.swarm.md`](https://github.com/EvolutionAPI/evo-nexus/blob/main/README.swarm.md) for the full Swarm / Portainer deployment guide and the `evonexus.stack.yml` template.
+
+### Local docker compose (building from source)
+
+If you're running `docker-compose.yml` locally (building the image from source instead of pulling from Docker Hub):
 
 ```bash
 cd /path/to/your/workspace

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "evo-nexus"
-version = "0.30.1"
+version = "0.30.2"
 description = "Unofficial open source toolkit for Claude Code — AI-powered business operating system"
 requires-python = ">=3.10"
 dependencies = [