Changelogforge

io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 3, 2026

根据已合并的拉取请求生成发布变更日志,按标签分组,以 Markdown 格式呈现。

AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。

原文描述

Render a release changelog from merged pull requests, grouped by label, in Markdown.

已验证STDIO仅桌面开发者工具

概览

Changelogforge 的本地 MCP 服务;无需登录;STDIO。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Changelogforge,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

changelogforge

A release is ready, the pull requests are merged, and now someone has to turn that list into the changelog section readers will actually scan. changelogforge does that one job: it takes the merged pull requests for a release, sorts them into labelled groups, and renders the section as Markdown in a fixed, predictable shape.

  • Grouping by label — each pull request joins the first label in group_order that it carries. The default order is feature, bugfix, documentation, maintenance, and you can supply your own list to rename, reorder, add, or drop groups. Matching is exact and case-sensitive.
  • An other group — a pull request carrying none of the group labels lands in a final group whose heading is Other changes. Groups that end up empty are left out entirely, and the other group only appears when it has something in it.
  • Stable ordering — groups follow group_order with the other group always last, and inside a group the pull requests are sorted by number ascending, so the same input always renders the same section.
  • Exact Markdown — the version heading sits at heading_level (default 2) and group headings one level deeper. The result also returns the grouped structure itself, so a caller can render the same data another way.

Version and date are printed in the heading exactly as given; neither is parsed or reformatted. Pull request numbers must be unique across the list — a repeat is a validation error naming both occurrences, for example pull_requests[2].number duplicates pull_requests[0].number — and every other malformed field is likewise an error naming its path, with no partial section produced. The computation is pure and local: no network, no configuration, no files read beyond the input you pass in.

CLI

bash
npx @reneturcios/changelogforge generate --input args.jsonnpx @reneturcios/changelogforge --version

args.json contains the full arguments object:

json
{  "version": "1.2.0",  "date": "2026-10-27",  "pull_requests": [    { "number": 7, "title": "Add export button", "labels": ["feature"] },    { "number": 12, "title": "Fix crash on empty input", "labels": ["bugfix"] },    { "number": 15, "title": "Tidy internals" }  ]}

labels defaults to [] per pull request, group_order to ["feature", "bugfix", "documentation", "maintenance"], and heading_level to 2. The rendered section is printed as JSON:

json
{  "version": "1.2.0",  "date": "2026-10-27",  "groups": [    { "group": "feature", "heading": "feature", "pull_requests": [{ "number": 7, "title": "Add export button" }] },    { "group": "bugfix", "heading": "bugfix", "pull_requests": [{ "number": 12, "title": "Fix crash on empty input" }] },    { "group": "other", "heading": "Other changes", "pull_requests": [{ "number": 15, "title": "Tidy internals" }] }  ],  "markdown": "## 1.2.0 (2026-10-27)\n\n### feature\n\n- Add export button (#7)\n\n### bugfix\n\n- Fix crash on empty input (#12)\n\n### Other changes\n\n- Tidy internals (#15)",  "total_pull_requests": 3}

Exit codes: 0 on success, 1 on a runtime error (including an unreadable or invalid input file, or invalid input), 2 on a usage error.

MCP server

bash
npx -y @reneturcios/changelogforge mcp

MCP client config:

json
{  "mcpServers": {    "changelogforge": {      "command": "npx",      "args": ["-y", "@reneturcios/changelogforge", "mcp"]    }  }}

Tools

  • generate_changelog — Render a release changelog section from merged pull requests, grouped by label.

    • version (string, required) — release version label, printed verbatim in the heading
    • date (string, required) — release date, printed verbatim in the heading
    • pull_requests (array, required, at least one) — merged pull requests as {number, title, labels?} objects; number is unique across the list
    • group_order (array of strings, optional) — labels that define groups, in output order
    • heading_level (integer, optional, 1–5) — Markdown heading level for the version heading

    Returns {version, date, groups, markdown, total_pull_requests}.

Docker

bash
docker run -i ghcr.io/cloudcorprecords/changelogforgedocker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/changelogforge generate --input /w/args.json

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # tsx --test test/*.test.ts (pure local, no network)npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios

来源:README.md,提交 27adce7

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.0最新Nov 3, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分