# Release Notes

Create release notes for a new version tag.

- Repository: https://github.com/agentic-community/mcp-gateway-registry (1032 stars)
- Category: Writing
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add agentic-community/mcp-gateway-registry --skill release-notes -g -a claude-code -y`
Codex: `npx skills add agentic-community/mcp-gateway-registry --skill release-notes -g -a codex -y`
Cursor: `npx skills add agentic-community/mcp-gateway-registry --skill release-notes -g -a cursor -y`
Gemini CLI: `npx skills add agentic-community/mcp-gateway-registry --skill release-notes -g -a gemini-cli -y`

## Description

Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Release Notes Skill

Use this skill when the user wants to create release notes for a new version. This skill gathers all changes since a previous release, writes structured release notes following the project's established format, tags the repo, and pushes.

## Input

The skill takes a version tag as input:
- Format: `{major}.{minor}.{patch}` (e.g., `1.24.0`) - **no `v` prefix**, semver only
- Older releases (pre-`1.23.0`) used a `v` prefix (e.g., `v1.0.22`) - existing artifacts under `docs/release-notes/v*.md` and tags `v1.0.x` are preserved as-is, but **new releases must use the bare-semver convention**
- If the user provides a `v`-prefixed version for a new release, strip the prefix and confirm

## Output

Creates a release notes file in `docs/release-notes/` and tags the repo:
- `docs/release-notes/{version}.md` - Release notes markdown file (e.g., `docs/release-notes/1.24.0.md`)
- Git tag `{version}` pointing to the commit that includes the release notes

## Workflow

### Step 0: Confirm the Pre-Release Smoke Test Was Run (Gate)

Before doing any release-notes work, confirm the end-to-end release smoke test
([tests/e2e_release_test.py](../../../tests/e2e_release_test.py)) has been run
against a live gateway and passed. This suite exercises the surface a release
must not break: the registry is up, the built-in `airegistry-tools` server is
healthy and its search tool works, servers/agents/skills support full CRUD,
semantic search returns results, security scans run, and one real external MCP
server (AWS knowledge base) is reachable end to end through the gateway proxy.

1. **Ask the user, using AskUserQuestion**, whether they have already run the
   release smoke test and it passed. Offer these options:
   - "Yes, it passed" (proceed to Step 1)
   - "No, run it now" (Recommended - run it for them, see below)
   - "Skip it" (proceed, but see the warning below)

The rest: https://github.com/agentic-community/mcp-gateway-registry/blob/HEAD/.claude/skills/release-notes/SKILL.md