Skip to content

chore(release): merge v2/main into main for v2.10.1 - #2657

Merged
cliffhall merged 10 commits into
mainfrom
v2/chore/milestone-merge-v2.10.1
Oct 8, 2026
Merged

cliffhall merged 10 commits into
mainfrom
v2/chore/milestone-merge-v2.10.1

Conversation

@cliffhall

@cliffhall cliffhall commented Oct 8, 2026 •

Copy link
Copy Markdown
Member

Closes #2654

Milestone merge of v2/main into main for the v2.10.1 patch release, which is step 2 of the release skill. 2.10.1 fixes #2651: on 2.10.0, npx @modelcontextprotocol/inspector fails with "could not determine executable to run".

This is a pure merge

$ git rev-list HEAD --not origin/main origin/v2/main
d2a4be55 chore: merge v2/main into main for the v2.10.1 release
895e57a9 chore: merge v2/main into main for the v2.10.1 release
#   two merges: review of this PR found #2658 (fixed by #2659 on v2/main), re-merged

$ git rev-parse origin/v2/main^{tree}
d5fb57a8ac7f0504dbe0003a4f94e6f4492d701b
$ git rev-parse HEAD^{tree}
d5fb57a8ac7f0504dbe0003a4f94e6f4492d701b

The merged tree is byte-identical to origin/v2/main and reads 2.10.1, bumped on v2/main in #2653 / PR #2655. The payload since 2.10.0 is PR #2652 (the inspector bin alias, its two guards, and the README's mcpdo entry) plus the bump.

Verification

Ledger: https://claude.ai/artifact/NKoqS9ANaGb6Yx5ANPdcdU (for maintainer review; one row per closed milestone issue, with what was run and what was observed)

  • npm run local:gate on this tree passes every stage except smoke:web:firefox. That stage cannot launch Playwright's Firefox on macOS 27 (smoke:web:firefox cannot launch Playwright's Firefox on macOS 27 #2625). The three Firefox smokes were run from a clean export of this exact tree in the Linux Playwright container, and all passed. Storybook (529) was run separately, since the Firefox failure stops the gate chain before that stage.
  • npm run pack:verify: OK (27 files, 5.70 MB unpacked), including its new npm exec @modelcontextprotocol/inspector step.
  • npm audit: 0 vulnerabilities in all six installs.
  • 3 / 3 milestone issues driven from the packed tarball:
    • Before: a bare npx of the published 2.10.0 fails.
    • After: npx -y file:<tgz> and npm exec @modelcontextprotocol/inspector both run the launcher.
    • Version: web, CLI and mcpdo all report 2.10.1.

Found by review, fixed on v2/main

🤖 Generated with Claude Code

cliffhall and others added 7 commits October 7, 2026 23:28
…inspector` bin alias (#2651)

2.10.0 added `mcpdo` as a second bin. With more than one distinct bin,
npm's npx/exec runs only the bin named after the unscoped package name
(`inspector`), which didn't exist, so the documented entry point failed
with "could not determine executable to run".

Add `inspector` -> the launcher, and guard it twice: an offline
test:scripts check that the root manifest's npx default bin is the
launcher (mirrors libnpmexec's getBinFromManifest), and a pack:verify
step that runs the installed tarball via `npm exec` instead of by bin
name, which is why every existing check stayed green.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: cliffhall <cliff@futurescale.com>
…2651)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: cliffhall <cliff@futurescale.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: cliffhall <cliff@futurescale.com>
…fault-bin

fix(package): restore npx @modelcontextprotocol/inspector with an inspector bin alias
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: cliffhall <cliff@futurescale.com>
…-2-10-1

chore(release): 2.10.1 step 1 — audit, bump to 2.10.1
Copilot AI balanced review requested due to automatic review settings October 8, 2026 04:33
@cliffhall cliffhall added the v2 Issues and PRs for v2 label Oct 8, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The canonical publishing guide does not document the newly added release verification step.

1 open finding
What changed in this PR

Merges the v2.10.1 release payload into main, restoring bare npx invocation after adding the mcpdo binary.

Changes:

  • Adds the inspector launcher alias and bumps version to 2.10.1.
  • Adds offline and packaged-tarball verification of npm’s default-bin resolution.
  • Documents mcpdo and the launcher alias.
File Description
README.md Documents the fourth client and invocation command.
clients/​launcher/​README.md Explains the required inspector alias.
package.json Bumps the version and adds the alias.
package-lock.json Records manifest changes.
scripts/​lib/​npx-default-bin.mjs Mirrors npm’s bin-selection behavior.
scripts/​lib/​npx-default-bin.test.mjs Tests bin resolution and the root manifest.
scripts/​pack-and-verify.mjs Exercises default-bin selection from the installed tarball.

🧠 Review effort: Balanced


Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.

Comment thread scripts/pack-and-verify.mjs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: cliffhall <cliff@futurescale.com>
Copilot AI balanced review requested due to automatic review settings October 8, 2026 04:46
@cliffhall

Copy link
Copy Markdown
Member Author

Copilot round 1: 1 finding (publishing guide omitted the new pack:verify step). Fixed on v2/main via #2658 / PR #2659 and re-merged as d2a4be5; tree still byte-identical to origin/v2/main (d5fb57a8). Ledger updated. Requesting round 2.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The release payload is consistent, adequately tested, and the prior documentation gap is resolved.

0 open findings

1 resolved since last review

🧠 Review effort: Balanced


Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.

@cliffhall

Copy link
Copy Markdown
Member Author

Copilot review loop closed: round 2 (at d2a4be5) was clean — 0 inline comments, nothing in the headline or a suppressed block; the round-1 finding (#2658) is resolved.

@cliffhall
cliffhall merged commit 0d2bc1d into main Oct 8, 2026
9 checks passed
@cliffhall
cliffhall deleted the v2/chore/milestone-merge-v2.10.1 branch October 8, 2026 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v2 Issues and PRs for v2

Projects

None yet

2 participants