Forgeprint

Catalog entries are written once, in English. Your browser can translate them.

← all crews

crews/release-crew

Release Crew

Assembled by @aliosmanmho

A release cut the same way every time: a version derived from history, a gate whose red means stop, a rollout with a rollback somebody has run, and a watch on the error budget afterwards.

Claude Code Codex CLI GitHub Copilot CLI Cursor Gemini CLI Windsurf Cline OpenCode Kiro

What it is for

Cutting a release of a running service: version and changelog derived from the history, the release gate, a staged rollout with tested rollback criteria, and post-deploy checks against the SLO.

Where it is wrong

Feature design, building infrastructure from nothing, or a routine patch release one agent can follow the release-manager checklist through in order. Sequential, small work is worse with more agents, not better.

Members

Integrations

Read it

README.md

Use it

Ask an agent connected to the Forgeprint MCP for get_crew with this slug. A crew is a recommendation with a name on it, not a requirement. get_crew { "slug": "release-crew" }