# Making A Release

> Use when a developer wants to cut, publish, or ship a new release of the CodeScene MCP Server, or asks how to make a release / bump the version.

- Skill: `codescene-oss/making-a-release` (Agent Skill)
- Install (CLI): `npx skillmds@latest add codescene-oss/making-a-release`
- Raw SKILL.md: https://api.skillmd.com/api/skills/codescene-oss/making-a-release/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: codescene-oss (https://skillmd.com/u/codescene-oss)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/codescene-oss/making-a-release

---


# Making a Release

To release the CodeScene MCP Server, create and push an annotated `MCP-<version>`
tag. That single push is the entire process — CI does everything else (release
notes, binaries, Docker, npm, packaging metadata, and marking it latest).

1. Decide the next version following semver. The latest release is the most
   recent `MCP-<version>` tag.
2. Make sure the commit you tag (normally the tip of `main`) is exactly what you
   want to ship.
3. Create and push the tag (keep the `MCP-` prefix — CI only triggers on
   `MCP-*` tags):
   ```sh
   git tag -a MCP-1.4.3 -m "Release MCP-1.4.3"
   git push origin MCP-1.4.3
   ```

Do not bump version files, edit the changelog, draft the release in the GitHub
UI, or open any PRs — CI handles all of it.