Release Notes Generator

Write release notes from a commit log or changelog, with Added, Changed, Fixed and Removed sections.

Pay by wallet (x402) AI-generated release-notes-generate

Example

Input
{
  "commits": "test_value"
}
Answer
{
  "date": "2026-03-09",
  "summary": "Test release with minimal changes",
  "version": "NEXT",
  "markdown": "## Changed\n\n- test_value\n",
  "sections": {
    "added": [],
    "fixed": [],
    "changed": [
      "test_value"
    ],
    "removed": [],
    "security": [],
    "deprecated": []
  },
  "contributors": [],
  "breaking_changes": []
}

Inputs

FieldTypeRequiredWhat it is
commitsstringYes—
versionstringNo—

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
summarystringAlways (present in every successful answer)
versionstringAlways (present in every successful answer)
markdownstringAlways (present in every successful answer)
sectionsobjectAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "release-notes-generate",
    "inputs": {
      "commits": "test_value"
    },
    "max_price_cents": 3
  }'

Limitations

  • Unmarked breaking changes can be missed

    Generated from commits or changelogs — breaking changes may not be prominently flagged without conventional commit markers

    What to do instead: Use breaking change prefixes (BREAKING CHANGE:, feat!:) in commits for accurate breaking change detection