Repository navigation
chore: bump version to 1.0.3 - #2754
Merged
Merged
Conversation
Releases the pending v1 security and hygiene fixes. Version fields only — no functional change. The lockfile version fields were edited directly rather than via `npm run update-version`, which finishes with a bare `npm install` that re-resolves the whole tree, matching the 1.0.2 bump (#2081). Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Signed-off-by: cliffhall <[email protected]>
4 tasks
There was a problem hiding this comment.
🔵 Needs a closer look
A maintainer must confirm the private prerequisite security fixes have landed before merging this release bump.
No open issues 🎉
What changed in this PR
Prepares MCP Inspector v1.0.3 for release after the pending security fixes land, with no functional changes.
Changes:
- Bumps all four package versions to
1.0.3. - Aligns workspace dependency ranges and lockfile metadata without re-resolving dependencies.
| File | Description |
|---|---|
| server/package.json | Bumps server version to 1.0.3. |
| package.json | Updates root version and workspace dependency ranges. |
| package-lock.json | Synchronizes package versions and dependency ranges. |
| client/package.json | Bumps client version to 1.0.3. |
| cli/package.json | Bumps CLI version to 1.0.3. |
Review effort: Balanced
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 #2753
Change
Version fields only, no functional change.
versionbumped 1.0.2 -> 1.0.3 inpackage.json,client/,server/,cli/@modelcontextprotocol/inspector-*workspace dependency ranges in the rootpackage.json(^1.0.2->^1.0.3)versionfields inpackage-lock.json15 insertions, 15 deletions across 5 files.
Merge order
Merge after the pending fixes have landed on
v1/main, so 1.0.3 contains them. Those changes are tracked privately until they are published; the release notes will list them.Note on
npm run update-versionNot used, for the same reason as #2081: its trailing bare
npm installre-resolves the whole tree. The 8 lockfileversionfields were edited directly.Verification
npm run check-versionpasses (all 4 packages at 1.0.3; ranges and lock version consistent)npm ciaccepts the lockfile and leaves it unmodifiednpm run build,npm run lintandnpm run prettier-checkpassPost-merge
Tag
v1.0.3onv1/mainand publish a GitHub release for it. The release event'spublishjob runsnpm run publish-allto thev1-latestdist-tag.🤖 Generated with Claude Code