release

A release procedure for Memoria that updates the version, creates the changelog, tags and pushes the code, and lets CI build binaries, Docker images, and a GitHub release.

In plain words
What is it for?
Use it to publish a Memoria stable release, release candidate, or Docker image.
Why use it?
It turns the versioning and publishing steps into a defined flow for stable and pre-release versions.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/matrixorigin/memoria/release
Any agent
npx skills add matrixorigin/memoria --skill release
Clone the repo
git clone --depth 1 https://github.com/matrixorigin/memoria

Made for: Claude Code, Codex.

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 567 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00567
Opus 5 $0.00014 $0.00283
Sonnet 5 $0.00005 $0.00113
Haiku 4.5 $0.00003 $0.00057

Measured 2d ago against content hash ae5264a77201, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/release/SKILL.md · 69 lines

What it actually says

Flow

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

Stable 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).

Pre-Release

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: rc1rc2 → stable.

Manual Docker Push

make release-docker                  # :latest
make release-docker VERSION=0.2.0   # :0.2.0 + :latest

CI Workflows

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.

Version Locations

  • memoria/Cargo.toml — source of truth
  • memoria --version — binary
  • mcp.json_version field
  • Steering rules — <!-- memoria-version: x.y.z -->

Checklist

  • Clean working tree, CI green on main
  • README/docs updated for user-facing changes
  • Steering rules updated if tool behavior changed
  • make release VERSION=x.y.z
  • Verify GitHub Release has 4 binaries + checksums
  • Verify Docker Hub has new tag
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 69 lines · 27 tokens per session scan A ae5264a77201

Subscribe to this mod's changes

release is a skill published in the GitHub repository matrixorigin/memoria (592 stars, last pushed 6d ago), licensed Apache-2.0. It adds 27 tokens to every session and 567 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.