chore: bump version to 2.5.0 - #2213
Merged
Merged
Conversation
Bumps the root package.json from 2.4.0 to 2.5.0 on v2/main, ahead of the v2.5.0 milestone merge into main. Applied with `npm version minor --no-git-tag-version` — the tag is deliberately omitted because the release is cut from main, so the tag must point at the merge commit there rather than at a v2/main commit that is never released. Closes #2212 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017bussXiM47PBttWqFUkPN1 Signed-off-by: cliffhall <cliff@futurescale.com>
There was a problem hiding this comment.
🟢 Approval recommended
The manifest and lockfile versions are consistent and match the stated release scope.
Pull request overview
Bumps the Inspector release version from 2.4.0 to 2.5.0 ahead of the milestone merge.
Changes:
- Updates the root package version.
- Synchronizes lockfile metadata.
File summaries
| File | Description |
|---|---|
package.json |
Sets version to 2.5.0. |
package-lock.json |
Updates both root version fields. |
Review details
- Files reviewed: 1/2 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
3 tasks
This was referenced Sep 1, 2026
pull Bot
pushed a commit
to wei/mcp-inspector
that referenced
this pull request
Sep 2, 2026
The fifth v2/main -> main milestone merge, cutting 2.5.0: 33 merged PRs and 213 non-merge commits, including the 2.4.0 -> 2.5.0 version bump (modelcontextprotocol#2213), which landed on v2/main first per the modelcontextprotocol#2010 procedure. Zero conflicted paths, and the merged tree is byte-identical to origin/v2/main. References modelcontextprotocol#2214 Signed-off-by: Cliff Hall <cliff@futurescale.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017bussXiM47PBttWqFUkPN1 Signed-off-by: cliffhall <cliff@futurescale.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2212
Bumps the root
package.jsonversion from2.4.0to2.5.0onv2/main, ahead of the v2.5.0 milestone merge intomain.What changed
package.json:2.4.0→2.5.0package-lock.json: the two matchingversionfields, updated by npmThat is the whole diff — the repo has one version number, and the clients under
clients/*carry none.How
--no-git-tag-versionis load-bearing: a barenpm versionwould also create a tag, and it would land on av2/maincommit. The release is cut frommain, so the tag has to point at the milestone merge commit there — tagging here would produce a tag on a commit that is never released.Why the bump goes on
v2/mainfirstPer the
releaseskill and #2010: the bump is part of the milestone's work, so it belongs on the develop branch and flows intomainwith everything else. Doing it on the milestone-merge branch instead leaves the bump only downstream ofv2/main— which is howv2/mainsat at2.0.0through both the 2.1.0 and 2.2.0 releases, and how a2.0.0 → 2.2.0diff leaked into an unrelated container bugfix (#2009).Between this merge and the milestone merge,
v2/mainreading2.5.0whilemainstill reads2.4.0is expected — a release is in flight, not drift.Verification
npm run format— clean, no files rewrittennpm run local:gate— passes2.5.0git tag was createdNo user-facing behavior change, so no screenshots apply.