chore(deps): bump @ai-sdk/mcp from 1.0.52 to 2.0.20 - #1575
chore(deps): bump @ai-sdk/mcp from 1.0.52 to 2.0.20#1575dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@ai-sdk/mcp](https://github.com/vercel/ai/tree/HEAD/packages/mcp) from 1.0.52 to 2.0.20. - [Release notes](https://github.com/vercel/ai/releases) - [Changelog](https://github.com/vercel/ai/blob/main/packages/mcp/CHANGELOG.md) - [Commits](https://github.com/vercel/ai/commits/@ai-sdk/mcp@2.0.20/packages/mcp) --- updated-dependencies: - dependency-name: "@ai-sdk/mcp" dependency-version: 2.0.20 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5ddc878451
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@ai-sdk/azure": "~3.0.77", | ||
| "@ai-sdk/google": "~3.0.83", | ||
| "@ai-sdk/mcp": "1.0.52", | ||
| "@ai-sdk/mcp": "2.0.20", |
There was a problem hiding this comment.
Update the lockfile with the MCP bump
Bumping @ai-sdk/mcp here without committing the corresponding bun.lock change leaves the root lockfile pinned to @ai-sdk/mcp 1.0.52, so the dependency graph no longer matches package.json. The checked CI workflow installs with bun install --frozen-lockfile (.github/workflows/ci.yml), and Bun's help describes that flag as “Disallow changes to lockfile”, so every fresh CI/local frozen install for this commit has to fail instead of resolving 2.0.20. Please regenerate and commit the root bun.lock entry with this package update.
Useful? React with 👍 / 👎.
|
🤖 pr-fix routine: blocked — cannot regenerate Root cause of the 4 failing checksAll four failures ( This PR changes one line in This is not specific to this PR or to the major-version jump. #1568 (the Why this routine can't fix itThe fix is mechanical —
What a human needs to doAny of these resolves the whole backlog, not just this PR:
Separate concern for this PR specifically
The routine will not pick this PR up again until someone removes the Generated by Claude Code |
Bumps @ai-sdk/mcp from 1.0.52 to 2.0.20.
Release notes
Sourced from @ai-sdk/mcp's releases.
... (truncated)
Changelog
Sourced from @ai-sdk/mcp's changelog.
... (truncated)
Commits
eb3d1afVersion Packages (#18208)97f0565fix: MCP requests and client initialization can hang past configured deadline...a56fbc0Version Packages (#18083)232a45aVersion Packages (#18004)8fd84f0Version Packages (#17983)0319ff3Version Packages (#17553)9352ac1Version Packages (#17417)d84ea43fix: OAuth discovery rejects RFC-compliant metadata without PKCE method decla...b8241a6Version Packages (#17264)48e7e78fix(react/mcp): harden MCP Apps metadata handling and host/iframe bridge (#17...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)