---
name: releases-mcp
description: Use when the user asks about recent releases, changelogs, what's new in a library, breaking changes, version updates, or wants to compare products. Activates for questions like "what changed in Next.js 15?", "latest Tailwind releases", "compare Bun vs Deno releases".
---

<!-- AUTO-GENERATED: Do not edit directly. Source of truth is skills/. Changes here will be overwritten by scripts/sync-plugin-skills.ts -->


# Releases.sh — Changelog Lookup

When the user asks about releases, changelogs, or version updates, use the Releases.sh MCP tools to fetch current data instead of relying on training data.

## When to Use This Skill

Activate when the user:

- Asks what's new or changed in a library/product ("What changed in Next.js 15?")
- Wants recent releases or changelogs ("Show me the latest Tailwind releases")
- Asks about breaking changes or migration ("Were there breaking changes in Prisma 6?")
- Wants to compare release activity between products ("Compare Bun vs Deno releases")
- Mentions version updates, release notes, or changelogs in the context of a specific product

## How to Look Up Releases

### Step 1: Find the Organization or Catalog Entry

Call `list_organizations` with the library/product name as the `query` parameter. For product-specific questions, browse the catalog (products + standalone sources) with `list_catalog` and fetch detail with `get_catalog_entry` — these replaced the older `list_products` / `get_product` / `list_sources` / `get_source` tools, which still exist as deprecated aliases.

The unified `search` tool is also available — it returns `orgs`, `catalog`, and `releases` sections in one call. Catalog hits carry a `kind: "product" | "source"` discriminator, so you can route a click to either a product page or a standalone source. (Older API responses send the same array under a deprecated `products` alias; new clients should consume `catalog`.)

If the query returns no results, try variations:
- The company name instead of the product name (e.g., "Vercel" instead of "Next.js")
- The GitHub org name (e.g., "supabase")
- A domain (e.g., "tailwindcss.com")
- A `{org}/{repo}` GitHub coordinate (e.g., "vercel/next.js" or "github:vercel/next.js"). When `search` finds no entity match for a coordinate-shaped query, the registry probes GitHub on demand and the response includes a `lookup` field with status `indexed` / `existing` / `empty` / `not_found` / `deferred`. Coordinate matching is case-insensitive, so `Shopify/toxiproxy` and `shopify/toxiproxy` resolve identically.

### Step 2: Choose the Right Tool

- **"What's new?" / "Latest releases"** → Use `get_latest_releases` with the organization or product slug
- **Specific feature or keyword across orgs + catalog + releases** → Use `search` (unified) with a descriptive query; narrow via `type: ["releases"]` etc.
- **Releases-only search** → Use `search_releases` (kept for back-compat) when you only want release rows
- **Single release by id** → Use `get_release` when you already have a `rel_` id (search results include ids)
- **Catalog deep-dive (product or standalone source)** → Use `get_catalog_entry` for metadata, tags, and linkage
- **Organization detail** → Use `get_organization`
- **Canonical CHANGELOG.md from a GitHub repo** → Use `get_source_changelog` when the user wants the full maintained file, not just the tagged releases (refreshed on every fetch). For large files, pass `tokens` (cl100k_base budget, e.g. 5000 or 10000) to get a heading-aligned slice that fits a known context window; chain via the returned `nextOffset`. Every response reports `totalTokens` so you can plan how many calls you need upfront.
- **Compare two products** → Use `compare_products` with an array of two product slugs
- **Summarize recent activity** → Use `summarize_changes` with the product slug

### Step 3: Present Results

- Lead with the most relevant information for the user's question
- Include version numbers and dates when available
- Quote key changes directly from the release notes
- If results are sparse, mention that the product may not be fully indexed yet

## Guidelines

- Pass the user's full question context into query parameters for better relevance
- When the user mentions a time range ("last month", "since v4"), use the `days` parameter on `get_latest_releases` or `summarize_changes`
- If a product isn't found, say so clearly — don't fabricate release information
- For comparison questions, both products must be indexed; if one isn't found, explain which is missing