Skip to content

Releases

Where Latest
Ramen GitHub releases, tagged v<version> with zips built by CI latest
ramen-mcp-bridge PyPI and GitHub 1.0.0
ramen-demo-mcp GitHub, the demo group repo tagged v<version> with each Ramen release
Images Docker Hub bkraad47/ramen-worker, bkraad47/ramen-console; the same on ghcr.io/bkraad47/ <version> and latest
uvx ramen-mcp-bridge@latest      # or: pip install ramen-mcp-bridge==1.0.0
docker pull bkraad47/ramen-worker:latest bkraad47/ramen-console:latest

Which versions go together

Ramen Bridge on PyPI Demo repo Notes
1.0.0 1.0.0 (TLS by default, the policy bundle; 0.3.x cannot pass a Required policy) v1.0.0 tag: confirm_delete_note (asks before it deletes), slow_report ("task": true), golden cases with respond MCP spec 2026-07-28 next to 2025-06-18 on the same endpoint: stateless requests, standard headers, multi round-trip requests, tasks, subscriptions/listen; 2025-06-18 clients answered as in 0.8.0; the group contract only gains optional additions. What changes for existing users
0.8.0 0.3.0 v0.8.0 tag (same tools and rails as v0.7.5) the security review's fixes (repo_url validation, no repo-shipped deploy file, loopback redirect check, one autoscale decision per zone, no concurrent deploys, trusted-hop audit ip); the compose stack pulls the published images; worker, Glama and MCPB images pin bridge 0.3.0; no static secrets; verified again on GKE, EKS and AKS
0.7.5 0.2.2 in the worker image; 0.3.0 documented, on PyPI since 2026-10-17 v0.7.5 tag: mcp/guardrails.yaml, NeMo rails, word_count guardrails in the runtime, identity-provider group lookup, custom roles, AKS, autoscaling by Ramen, salted hashes
0.7.0 to 0.7.2 0.2.2 v0.7.0 to v0.7.2 tags: mcp/tests.yaml, output schemas, richer descriptions gates, golden cases, output schemas (0.7.0); per-tool access, rollout notice, drift (0.7.2)
0.6.23 0.2.2 main with mcp/env.yaml and .github/workflows/ramen-deploy.yml self-contained image for MCP directories (glama/Dockerfile); Smithery bundle mcpb/; no worker or bridge change
0.6.21 0.2.2 main with mcp/env.yaml and .github/workflows/ramen-deploy.yml new MCP registry title and description; no worker or bridge change
0.6.2 0.2.2 main with mcp/env.yaml and .github/workflows/ramen-deploy.yml listed on the official MCP registry as io.github.bkraad47/ramen; no worker or bridge change
0.6.1 0.2.2 main with mcp/env.yaml and .github/workflows/ramen-deploy.yml the worker image installs bridge 0.2.2: Windows token file in %LOCALAPPDATA% (0.2.1), --ca also verifies the console during --oauth (0.2.2)
0.6.0 0.2.0 main with mcp/env.yaml env.yaml is new and optional; the worker image installs bridge 0.2.0
0.5.95 0.2.0 main the bridge gained --oauth
0.5.93 0.1.0 main OAuth role mapping, mcp_user, scoped permissions
0.5.7 to 0.5.8 0.1.0 main the bridge moved to its own package and was server-tested on both clouds
0.5.6 and earlier in ramen/runtime-py main

The bridge speaks ramen.v1.Mcp/Call, unchanged since 0.3.1, so any bridge works against any worker from 0.3.1 on. It forwards each message as it is, so a 2026-07-28 client behind it is served as 2026-07-28 by a 1.0 worker. --oauth needs a console from 0.5.95. The demo repo follows the group repo contract, unchanged since 0.1.0 except for additions.

Where a release is published

Pushing a v<version> tag runs the release workflow. Only the maintainer's own tags on bkraad47/ramen publish beyond GitHub (github.actor == 'bkraad47'); forks and other pushers stop after the GitHub release.

Channel How it updates
GitHub release zips, the MCPB bundle ramen-<version>.mcpb, and ramen-node-linux-amd64.zip (the latest worker, no version in the name)
Official MCP registry server.json published with GitHub OIDC; no secret
Smithery not updated: Smithery shut down its API, CLI and accounts on 2026-10-31 and refuses updates (403), so the release no longer publishes there (1.0.0)
Glama rebuilds from the repository and downloads the latest release's worker; nothing to publish
Docker Hub bkraad47/ramen-worker, bkraad47/ramen-console and GHCR ghcr.io/bkraad47/… (0.7.0) multi-arch images tagged <version> and latest; GHCR with the workflow's own token, Docker Hub with DOCKERHUB_USERNAME/DOCKERHUB_TOKEN (skipped with a warning when unset). Any cloud can pull them straight, without make push; since 0.8.0 the local compose stack pulls them by default (make up BUILD=1 builds from source)
Demo repo tag ramen-demo-mcp-group is tagged v<version> with the release it was verified against (VERSION file in the repo)
PulseMCP and other directories read the official registry

How a release is made (since 0.7.0)

  1. Work on branch v<version> (ramen, and the demo repo when it changes); test locally.
  2. Open a pull request to main; CI runs lint, versions, Python, Rust, conformance on Linux and Windows, the official MCP conformance suite for both protocol versions (1.0), kind.
  3. Merge when green. The merge runs ci again and pages (the docs site).
  4. Tag main with v<version> (the demo repo too). The tag runs release, which publishes everything in the table. Nothing goes to main without a pull request.

check_versions.py fails CI when server.json or the bundle is not at VERSION, or a description is over the registry's 100 characters, because a registry version cannot be changed once published.

Every release

The version tracker is generated from the changelog with a date and a release link per version. The architecture page keeps a snapshot per minor release.