Skip to content

0.28.0: version, changelog, Action pins; the PR comment checks toolmenu mcp - #77

Merged
niksa90 merged 3 commits into
mainfrom
claude/charming-brahmagupta-be7glj
Nov 11, 2026
Merged

niksa90 merged 3 commits into
mainfrom
claude/charming-brahmagupta-be7glj

Conversation

@niksa90

@niksa90 niksa90 commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

What

  • 0.28.0:
    • package.json, package-lock.json and server.json (version, and the package's version).
    • CHANGELOG.md: Unreleased becomes 0.28.0, with the weekly bench's --read-resources and the build-vendors.py kind fix under Repository.
    • The Action pin niksa90/toolmenu@v0.28.0 in README.md, docs/github-action.md and docs/ci.md. That includes the three docs/github-action.md examples still on v0.16.1.
  • The PR comment: the action job runs the Action twice.
    • On the fixture test/fixtures/sdk-server.mjs (three tools) with comment: 'false', still testing the Action.
    • On node dist/cli.js mcp against the new docs/toolmenu-menu.json; this run posts the comment.
  • test/mcp.test.mjs fails when docs/toolmenu-menu.json or docs/toolmenu-badge.json no longer match the server. The command in AGENTS.md writes both.
  • docs/RULES.md: the lists/resource-unread row says "something the run lacks", as the code does.

Why

0.28.0: snapshot --read-resources and its three rules are a new flag and new rules, so a minor version. It also carries the apps/resource fix for reads that failed for the run's reasons.

The PR comment: the Action keeps one comment per PR, and the only run here was the fixture's. Every PR reported "3 tools", never toolmenu's own six.

Tests

  • npm test: 725 passing. node dist/cli.js --version prints 0.28.0.
  • This PR's CI: all six jobs pass. The comment is the toolmenu mcp run: 6 → 6 tools, verdict unchanged, the dry-run hint only.
  • Two menu files that differ only in serverInfo.version give no diff finding, so a release bump doesn't make the comment report a change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014kCPJXf7SykHNoEUW3LYNt
@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

toolmenu

Verdict: ✓ unchanged: the same menu and the same findings. Nothing to accept. Findings against the baseline: 0 new, 0 gone, 0 changed.

toolmenu diff: toolmenu 0.28.0 → 0.28.0 (server-reported)

No breaking changes · 0 minor · 0 notices · ±0 tokens (~1,523 → ~1,523, estimate) · 6 → 6 tools

Version: suggested bump: none · not checked (set the Action's release input old..new)

No findings.

✓ 0 errors, 0 warnings, 0 info

Baseline: docs/toolmenu-menu.json in this checkout

toolmenu snapshot: toolmenu 0.28.0

Protocol 2026-07-28 · 6 tools · ~1,523 tokens (estimate)

1 info
Rule Finding
info write/no-dry-run · unsure 2 tools are annotated as destructive, and toolmenu found no dry_run/preview-style parameter and no preview tool for the same thing. Where a mistake is costly to undo, a dry run lets the agent see what would change while it can still back out. · snapshot_menu, check_session
→ Next: Where the effect is hard to undo, add a dry_run parameter that returns what would change without changing it. If it's cheap to undo, or a preview exists under another name, ignore this.

0 errors, 0 warnings, 1 info

Where the tokens go (estimate): the top 5 tools are 93% of the menu
Share Tool Tokens Description Schema
30% snapshot_menu ~461 ~99 ~353
26% check_session ~394 ~102 ~283
15% review_baseline ~231 ~65 ~156
12% diff_menus ~187 ~39 ~138
10% check_auth ~149 ~86 ~54
  • repeated: cwd (~37 tokens) in 4 tools, ~148 in all

A tool's schema can't $ref another tool's, so a block shared across tools is paid once per tool: only a smaller block saves tokens there.

toolmenu · token counts are estimates

The Action's PR comment came from its dogfood run on
test/fixtures/sdk-server.mjs, three tools, so every PR here reported
"3 tools" and never toolmenu's own server. The Action keeps one comment
per PR, so the fixture run (still testing the Action) now posts none, and
a second run on `node dist/cli.js mcp` against the new
docs/toolmenu-menu.json posts it: 6 tools, the dry-run hint, and a diff
for any PR that changes a tool's name, description or schema.

test/mcp.test.mjs fails when docs/toolmenu-menu.json or the badge no
longer match the server; AGENTS.md's command writes both. A version bump
alone is no difference (diff reports nothing).

Tests: npm test, 725 passing. action/run.sh on toolmenu mcp with that
baseline: verdict unchanged, 6 → 6 tools.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014kCPJXf7SykHNoEUW3LYNt
@niksa90 niksa90 changed the title 0.28.0: version, changelog, Action pins 0.28.0, and the PR comment is toolmenu mcp's own menu Nov 11, 2026
CHANGELOG 0.28.0 gains the weekly bench's --read-resources and the
build-vendors.py kind fix, and loses a broken line. The three examples in
docs/github-action.md that still pinned v0.16.1 pin v0.28.0. The
lists/resource-unread row says what the code says: something the run
lacks, not the machine.
@niksa90 niksa90 changed the title 0.28.0, and the PR comment is toolmenu mcp's own menu 0.28.0: version, changelog, Action pins; the PR comment checks toolmenu mcp Nov 11, 2026
@niksa90
niksa90 merged commit e278bae into main Nov 11, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants