update-harness-dependencies

Name: update-harness-dependencies
Availability: InStock
Author: Vercel

Update primary SDK dependencies of harness adapter packages using pnpm commands.

26.5k|5.1k|Updated May 23, 2023

Search Tags:#package management #SDK #pnpm #Monorepo #harness #lockfile #dependency update

Ready to run

npx skills add https://github.com/vercel/ai --skill update-harness-dependencies

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-harness-dependencies
Source: https://github.com/vercel/ai/tree/main/skills/update-harness-dependencies
Command: npx skills add https://github.com/vercel/ai --skill update-harness-dependencies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Harness adapter packages in the monorepo depend on third-party SDKs that must be kept current, and manually tracking which packages to update across many harnesses is error-prone and tedious.

Core Features & Use Cases

Guided dependency updates: Provides exact pnpm commands to update each harness's primary SDK packages, covering both bridge and non-bridge harnesses.
Bridge dependency handling: Includes separate commands for bridge dependencies that require the --ignore-workspace flag and a minimumReleaseAge config matching pnpm-workspace.yaml.
Version alignment verification: Directs you to run the verify-harness-adapter-deps.mjs script to confirm all dependency versions are aligned, including example app dependencies.
Use Case: When a new version of the Claude Agent SDK or Codex SDK is released, use this Skill to update the corresponding harness package, its bridge, and the e2e example dependencies in one consistent pass.

Quick Start

Update the harness SDK dependencies to their latest versions and verify that all adapter dependency versions are aligned.

Frequently Asked Questions about update-harness-dependencies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I update harness SDK dependencies in the Vercel AI monorepo?▼

Run the pnpm --filter harness-<name> update commands with --latest --lockfile-only for each harness package. For bridge harnesses, also run the bridge-specific update commands with --ignore-workspace and the minimumReleaseAge config flag.

What is the difference between bridge and non-bridge harness dependency updates?▼

Bridge harnesses like Claude Code keep SDK packages in devDependencies, with actual runtime versions managed inside the bridge directory. Non-bridge harnesses like Pi update packages directly in dependencies, so only bridge harnesses need the extra --ignore-workspace commands.

Why is the minimumReleaseAge flag needed for bridge dependency updates?▼

Bridge updates use --ignore-workspace, which bypasses the workspace-level pnpm-workspace.yaml settings. The --config.minimumReleaseAge=4320 flag must be passed explicitly so the minimum release age policy still applies to those updates.

How do I verify harness adapter dependency versions are aligned?▼

Run ./tools/verify-harness-adapter-deps.mjs from the repository root. If it reports errors, fix the mismatched versions and rerun the script until it passes.

Which harness packages do not need SDK version updates?▼

The harness-cursor and harness-fx adapters use unversioned installer scripts instead of NPM packages for their SDK or CLI, so they can be ignored during dependency update runs.