Bump @modelcontextprotocol/sdk from 1.9.0 to 1.26.0 in /observability/tasks/shared/mcp-servers/plane#7
Conversation
Bumps [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk) from 1.9.0 to 1.26.0. - [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases) - [Commits](modelcontextprotocol/typescript-sdk@1.9.0...v1.26.0) --- updated-dependencies: - dependency-name: "@modelcontextprotocol/sdk" dependency-version: 1.26.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/observability/tasks/shared/mcp-servers/plane/modelcontextprotocol/sdk-1.26.0
branch
from
1fa8fa6 to
54aeb4f
Compare
dependabot
bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| "funding": { | ||
| "url": "https://github.com/sponsors/colinhacks" | ||
| } | ||
| }, |
There was a problem hiding this comment.
Unsatisfied zod peer dependency causes dual-version incompatibility
High Severity
The SDK v1.26.0 declares zod as a non-optional peer dependency requiring ^3.25 || ^4.0, but the project only provides zod@3.24.2 (devDependency ^3.24.2). This causes npm to install a nested zod@4.3.6 under the SDK while the root stays at 3.24.2. All tool files (e.g. issues.ts, cycles.ts) do import { z } from "zod" getting zod 3.24.2, then pass those schemas to server.tool(), which the SDK processes with its nested zod-to-json-schema@3.25.2 (requiring zod ^3.25.28 || ^4). Since zod 4 is a ground-up rewrite with different internal _def structures, the SDK's schema-to-JSON conversion is likely to fail on zod 3.24.2 schema objects, potentially preventing tool registration or causing runtime errors.
Additional Locations (1)
Bumps @modelcontextprotocol/sdk from 1.9.0 to 1.26.0.
Release notes
Sourced from
@modelcontextprotocol/sdk's releases.... (truncated)
Commits
fe9c07bchore: bump version to 1.26.0 (#1479)4f01e7efix: add non-null assertions for optional setupServer fields in stateful testa05be17Merge commit from fork50d9fa3Fix #1430: Client Credentials providers scopes support (backported) (#1442)aa81a66fix(deps): resolve npm audit vulnerabilities and bump dependencies (v1.x back...6aba065chore: bump v1.25.3 for backport fixes (#1412)6e8f7e1fix: prevent Hono from overriding global Response object (v1.x) (#1411)12ae856[v1.x backport] Use correct schema for client sampling validation when tools ...b392f02fix: prevent ReDoS in UriTemplate regex patterns (v1.x backport) (#1365)a0c9b13fix: README badges links destinations (#907)Maintainer changes
This version was pushed to npm by pcarleton, a new releaser for
@modelcontextprotocol/sdksince your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.