Releases
The web app and the Telegram bridge are published as container images to GitHub Container Registry on every release.
Image tags
| Image | Purpose |
|---|---|
ghcr.io/ju-li/automata-mcp-web | Management UI and MCP endpoint |
ghcr.io/ju-li/automata-mcp-telegram-bridge | Telegram bridge |
Each release is tagged X.Y.Z, X.Y, X, latest, and sha-<commit>, built for linux/amd64. Evolution API is not an Automata image; pin it to evoapicloud/evolution-api:v2.3.7.
Pick a tag
Point services at :1, not :latest. The web service migrates its schema at boot and migrations only move forward, so a major release should never reach a deployment by accident on its next restart.
Use X.Y.Z when you need an exact, reproducible version, and sha-<commit> to run a specific commit. To run code that has not been released, build from the repository with the root directory at / and the Dockerfile at apps/web/Dockerfile or apps/telegram-bridge/Dockerfile.
Upgrading and rollback
- Back up Postgres.
- Pull the new image and restart the service.
- Confirm the web logs include
[app-db] applied migrations.
Because migrations only move forward, never roll back by running an older image against an upgraded database. Restore Postgres from the backup taken before the upgrade instead.
View source