// Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
| name | release |
| description | Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version. |
| Step | Who | How |
|---|---|---|
| Bump version, tag, push | You | make release VERSION=x.y.z |
| Build binaries (4 platforms) | CI | release-rust.yml |
| Build + push Docker image | CI | release-docker.yml |
| Create GitHub Release | CI | softprops/action-gh-release |
git status # Must be clean
make release VERSION=0.2.0
Does: update Cargo.toml version → cargo check → generate CHANGELOG (git-cliff) → commit → tag → push.
CI then: test → build binaries (x86_64/aarch64 linux/macos) → GitHub Release → Docker image (:0.2.0 + :latest).
make release-rc VERSION=0.2.0-rc1
Same but: no CHANGELOG, GitHub Release marked prerelease, Docker gets :0.2.0-rc1 (not :latest).
Typical: rc1 → rc2 → stable.
make release-docker # :latest
make release-docker VERSION=0.2.0 # :0.2.0 + :latest
| Workflow | Trigger | What |
|---|---|---|
test.yml | Push main/develop, PRs | check + clippy + tests |
pr-title.yml | PR open/edit | Conventional Commits validation |
release-rust.yml | Tag v* | Test → build → GitHub Release |
release-docker.yml | Tag v* | Test → build → Docker Hub |
Both release workflows run full test suite before publishing.
memoria/Cargo.toml — source of truthmemoria --version — binarymcp.json — _version field<!-- memoria-version: x.y.z -->make release VERSION=x.y.zUse Memoria as OpenClaw's durable memory slot. Triggers: "remember this", "save to memory", "what do you remember", "continue from last time", "forget this", "correct memory", "take a snapshot", "rollback memory", "branch memory", "merge memory", "use long-term memory".
Install Memoria and configure MCP for AI tools (Kiro, Cursor, Claude Code, Codex, Gemini CLI). Decision tree for Cloud vs self-hosted mode, database, embedding provider. Use when helping users set up Memoria.
Deploy Memoria with Docker Compose or Kubernetes. Environment variables, multi-instance setup, security. Use when deploying or configuring Memoria.
Memoria REST API endpoints, request/response formats, auth, rate limits. Use when calling or implementing API endpoints.
Memoria codebase structure, workspace layout, key traits, database tables, config patterns, and testing conventions. Use when navigating or modifying Memoria code.
Run embedding on-device with ONNX Runtime. Build from source, model selection, offline mode. Use when setting up local embedding without an API key.