Making a release
Skill codescene-oss/codescene-mcp-server/.agents/skills/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.From its SKILL.md
npx -y skills add codescene-oss/codescene-mcp-server --skill making-a-releaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
0.9 KB, as published. Nobody here has run it
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).
- Decide the next version following semver. The latest release is the most
recent
MCP-<version>tag. - Make sure the commit you tag (normally the tip of
main) is exactly what you want to ship. - Create and push the tag (keep the
MCP-prefix — CI only triggers onMCP-*tags):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.