Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 07:15 UTC
fix(ts/e2e): install `@composio/core` in vercel fixture setup (#5165)
This PR: - removes `"@composio/core": "file:/app/ts/packages/core"` from the `vercel-ai-sdk-v6` and `vercel-ai-sdk-v7` fixture manifests - installs `/app/ts/packages/core` in the fixtures' existing `install:vercel` script instead, the same way the `openai-zod4-compat` fixture installs its packages - inside the e2e container nothing changes: npm still links `@composio/core` to `/app/ts/packages/core` ## Context `/app/...` only exists inside the e2e Docker image. Dependabot scans every `package.json` in the repo, cannot resolve that absolute path and aborts the whole job with `path_dependencies_not_reachable: @composio/core at /app/ts/packages/core`. 107 of the last 300 Dependabot runs failed; the sampled failures are this error. One of them is the security-update job for a `next` advisory in `/docs`, which aborted before it could open its PR. `exclude-paths` in `dependabot.yml` would not help: GitHub documents it as applying to version updates only, and the failing job is a security update. ## How has this been tested? - `COMPOSIO_E2E_NODE_VERSION=24.22.1 pnpm --filter @e2e-tests/node-vercel-ai-sdk-v6 test:e2e:node`: 7 pass, 0 fail - `COMPOSIO_E2E_NODE_VERSION=24.22.1 pnpm --filter @e2e-tests/node-vercel-ai-sdk-v7 test:e2e:node`: 8 pass, 0 fail - no other `package.json` in the repo uses a `file:/app` dependency