Skip to content

chore(deps): bump @ai-sdk/mcp from 1.0.52 to 2.0.20 - #1575

Open
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/npm_and_yarn/dev/ai-sdk/mcp-2.0.20
Open

chore(deps): bump @ai-sdk/mcp from 1.0.52 to 2.0.20#1575
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/npm_and_yarn/dev/ai-sdk/mcp-2.0.20

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 3, 2026

Copy link
Copy Markdown
Contributor

Bumps @ai-sdk/mcp from 1.0.52 to 2.0.20.

Release notes

Sourced from @​ai-sdk/mcp's releases.

@​ai-sdk/voyage@​2.0.18

Patch Changes

  • Updated dependencies [5fc7da5]
  • Updated dependencies [93b2acd]
    • @​ai-sdk/provider-utils@​5.0.18

@​ai-sdk/voyage@​2.0.17

Patch Changes

  • Updated dependencies [fa95504]
    • @​ai-sdk/provider-utils@​5.0.17

@​ai-sdk/rsc@​1.0.227

Patch Changes

  • ai@5.0.225

@​ai-sdk/rsc@​1.0.226

Patch Changes

  • ai@5.0.224

@​ai-sdk/angular@​1.0.225

Patch Changes

  • ai@5.0.225

@​ai-sdk/langchain@​1.0.225

Patch Changes

  • ai@5.0.225

@​ai-sdk/llamaindex@​1.0.225

Patch Changes

  • ai@5.0.225

@​ai-sdk/harness-codex@​1.0.56

Patch Changes

  • @​ai-sdk/harness@​1.0.54

@​ai-sdk/harness-claude-code@​1.0.55

Patch Changes

  • @​ai-sdk/harness@​1.0.54

@​ai-sdk/harness-opencode@​1.0.55

Patch Changes

... (truncated)

Changelog

Sourced from @​ai-sdk/mcp's changelog.

2.0.20

Patch Changes

  • 97f0565: Honor MCP request deadlines and support bounding or aborting client initialization.
  • Updated dependencies [d8210b6]
  • Updated dependencies [b192878]
    • @​ai-sdk/provider-utils@​5.0.16

2.0.19

Patch Changes

  • Updated dependencies [1659cd5]
  • Updated dependencies [6a5bdff]
    • @​ai-sdk/provider-utils@​5.0.15

2.0.18

Patch Changes

  • Updated dependencies [0c464d9]
  • Updated dependencies [c49380c]
    • @​ai-sdk/provider-utils@​5.0.14

2.0.17

Patch Changes

  • Updated dependencies [1e2f324]
    • @​ai-sdk/provider@​4.0.4
    • @​ai-sdk/provider-utils@​5.0.13

2.0.16

Patch Changes

  • Updated dependencies [02ffdcb]
  • Updated dependencies [76cb673]
    • @​ai-sdk/provider-utils@​5.0.12

2.0.15

Patch Changes

  • d84ea43: fix(mcp): accept OAuth metadata without code challenge methods
  • Updated dependencies [cd06458]
    • @​ai-sdk/provider-utils@​5.0.11

2.0.14

... (truncated)

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 3, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot 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.

💡 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".

Comment thread package.json
"@ai-sdk/azure": "~3.0.77",
"@ai-sdk/google": "~3.0.83",
"@ai-sdk/mcp": "1.0.52",
"@ai-sdk/mcp": "2.0.20",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge 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 👍 / 👎.

Copy link
Copy Markdown
Member

🤖 pr-fix routine: blocked — cannot regenerate bun.lock in the routine sandbox

Root cause of the 4 failing checks

All four failures (Test, Lint, and Type Check, Validate CDK Infrastructure, Auth Edge Production Artifact, Unified Content PostgreSQL Lifecycle) die within ~45s at the same step:

bun install --frozen-lockfile
error: lockfile had changes, but lockfile is frozen
note: try re-running without --frozen-lockfile and commit the updated lockfile

This PR changes one line in package.json and nothing else — bun.lock was not updated. git log --author=dependabot -- bun.lock returns nothing, so Dependabot has never updated the Bun lockfile in this repo. Every root-package.json Dependabot PR is therefore red on arrival.

This is not specific to this PR or to the major-version jump. #1568 (the minor-and-patch group bump) shows the byte-identical failure signature, as does #1574. #1576 and #1563 were already marked stuck by earlier fires. By contrast, #1566 (/infra-only) passes Test, Lint, and Type Check because it never touches the root lockfile.

Why this routine can't fix it

The fix is mechanical — bun install and commit bun.lock — but it is not possible from the routine's sandbox:

  1. The npm registry is fully blocked here. Every request returns 403, for metadata and tarballs alike (lodash, next, ai, @ai-sdk/mcp all 403). Bun therefore cannot resolve @ai-sdk/mcp@2.0.20: error: GET https://registry.npmjs.org/@ai-sdk%2fmcp - 403 … failed to resolve. Without registry access the lockfile cannot be regenerated, and hand-writing an entry would mean fabricating an integrity hash — not something I'll do.
  2. The CI-pinned Bun version isn't installable here either. CI pins bun-version: "1.2.x"; both bun.sh and the npm bun package are 403. The sandbox's Bun 1.3.11 writes an extra "configVersion": 0 key into bun.lock, which is its own risk against a 1.2.x --frozen-lockfile run.

What a human needs to do

Any of these resolves the whole backlog, not just this PR:

  • Per PR (works today): check out the branch, run bun install, commit and push the updated bun.lock.
  • Systemic (recommended): add a CI step that regenerates and commits bun.lock on Dependabot PRs, or relax --frozen-lockfile for Dependabot-authored branches. ⚠️ Both live under .github/workflows/**, which this routine is explicitly forbidden from editing — autonomous runs cannot approve changes to workflow files.

Separate concern for this PR specifically

@ai-sdk/mcp 1.0.52 → 2.0.20 is a major bump, and the repo is on ai@6.0.240 (#1570 separately proposes ai 6 → 7). Even once the lockfile is valid, this one needs a real compatibility review rather than an automatic merge — worth sequencing against #1570.

The routine will not pick this PR up again until someone removes the pr-fix-stuck label.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code pr-fix-stuck pr-fix routine gave up — human attention needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant