Repository navigation
chore(deps): bump @ai-sdk/provider-utils from 2.2.8 to removed in /sdk/typescript/integration/fixtures/mastra-0 in the npm_and_yarn group across 1 directory - #955
dependabot[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
|
Thanks @dependabot[bot] for keeping our dependencies current! 🙌 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
@dependabot rebase |
Bumps the npm_and_yarn group with 1 update in the /sdk/typescript/integration/fixtures/mastra-0 directory: [@ai-sdk/provider-utils](https://github.com/vercel/ai/tree/HEAD/packages/provider-utils). Removes `@ai-sdk/provider-utils` --- updated-dependencies: - dependency-name: "@ai-sdk/provider-utils" dependency-version: dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
7cc7416 to
a716e81
Compare
|
pr-autopilot will not merge this automatically (commit Why:
A person needs to review and merge it. pr-autopilot · Codex in a locked-down container · traced by failproofai |
|
Superseded by #966, closing as part of that consolidation. This one moved #966 clears this fixture's fixable advisories without moving the framework ( |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
…le Dependabot alert (#966) * fix(sdk/typescript): clear the fixable fixture advisories, replacing #965 and #955 #965 moved @mastra/mcp to 2.7.0 in mastra-1, which peers on @mastra/core >=1.79.0 while the fixture stayed on 1.68.0, so `npm ci` failed ERESOLVE and took down every shard that installs it. #955 moved @mastra/core to 1.80.0 in mastra-0, off the floor that fixture holds, and @mastra/mcp@0.14.5 cannot install beside that either. mastra-1 takes the new versions with what they need: @mastra/core 1.81.0, @mastra/mcp 2.7.0, @mastra/memory 1.40.0. That brings @modelcontextprotocol/node 2.1.2 and @hono/node-server 2.1.6, and retires the @modelcontextprotocol/client, @modelcontextprotocol/server and argparse overrides. nextjs moves @mastra/core with it, because it compares each route's trace with this fixture's. mastra-0 stays on Mastra 0.x. @hono/node-server and systeminformation move in range. An override moves gaxios 7.1.3 -> 7.3.1, which gcp-metadata pins exactly and which no longer needs rimraf, so rimraf, glob, minimatch and 21 more packages leave the tree. deepmerge has no patched release. llamaindex-0.11, llamaindex-0.12 and nextjs reach it only through html-to-text 9, and html-to-text 10 replaced it with deepmerge-ts, so an override takes it out of the tree. mastra-0 and langchain-dup-core drop their nested zod 3 by overriding zod to their own zod 4. @mastra/mcp and @mastra/schema-compat read zod-from-json-schema-v3 only under a zod 3 root, and @langchain/core@0.3.80 imports only zod/v3 and zod/v4/core, which zod 4 also ships. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KYzGfYysR6TiCoMXnAMbW6 * fix(dependabot): stop security updates moving a floor through its parent #955 opened after .github/dependabot.yml ignored `@mastra/*` on mastra-0, and moved @mastra/core to 1.80.0 anyway. Its job log shows why: the package being updated was @ai-sdk/provider-utils, which nothing ignored, and removing it ran `npm install @mastra/core@1.80.0 --force`. The ignore then only took those names out of the PR's description. A range is read for the package being updated, not for a parent moved on its behalf. So @ai-sdk/provider-utils gets its own range on ai-4 and mastra-0. ai-4 lists the same package in its job, which has so far ended at zod's all_versions_ignored before checking it, so the range is there for when that stops being the case. ts-sdk-fixture-pins.test.ts now fails when a floor installing @ai-sdk/provider-utils 2 has no such range, when zod 3 appears outside the three fixtures SECURITY.md accepts it in, or when a nextjs framework pin leaves its twin, which Dependabot cannot keep together because it resolves one directory at a time. Each new assertion was broken on purpose to confirm it fails. SECURITY.md records the fix pattern this work relied on (override the parent to a release that no longer needs the package) and narrows the zod row to three fixtures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KYzGfYysR6TiCoMXnAMbW6 * docs(security): say what the nested zod's consumers actually do @mastra/mcp imports zod-from-json-schema-v3 eagerly and only calls it under a zod 3 root, and @langchain/core@0.3.80 does load zod/v3, now from zod 4's package. So "a nested copy that nothing in the fixture loads" was wrong. What holds is that those consumers do not need the old major. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KYzGfYysR6TiCoMXnAMbW6 --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Bumps the npm_and_yarn group with 1 update in the /sdk/typescript/integration/fixtures/mastra-0 directory: @ai-sdk/provider-utils.
Removes
@ai-sdk/provider-utils