Skip to content

Upgrade @vapi-ai/server-sdk to ^1.2.2#6

Open
mhar-vapi wants to merge 1 commit into
mainfrom
upgrade-server-sdk-to-1.2.2
Open

Upgrade @vapi-ai/server-sdk to ^1.2.2#6
mhar-vapi wants to merge 1 commit into
mainfrom
upgrade-server-sdk-to-1.2.2

Conversation

@mhar-vapi

@mhar-vapi mhar-vapi commented Jun 16, 2026

Copy link
Copy Markdown

Summary

  • Bump the package.json template in vapi-bootstrap-framework from @vapi-ai/server-sdk ^0.5.2 to ^1.2.2.
  • Update src/bootstrap.ts for the SDK 1.x API: import the Vapi namespace, type the build output as Vapi.CreateAssistantDto, and call assistants.update({ id, ...body }) (the 1.x signature) instead of update(id, body).
  • Bump skill metadata version from 1.0 to 1.1.

Test plan

  • In a fresh project, run the skill against a ROUGH_DRAFT.md and bun install — confirm @vapi-ai/server-sdk@1.2.x lands in node_modules.
  • bun run bootstrap (first run) — confirm assistants get created and ids print as before.
  • Paste the ids into .env.local and re-run — confirm Updated ... for every tuple (exercises the new update({ id, ...body }) path).
  • bun tsc --noEmit (or whatever the project uses) — confirm no type errors from the SDK 1.x bump.

Made with Cursor

The SDK's 1.x line changed `assistants.update` from `(id, body)` to a
single request object with the id inline, and exposes named DTO types
under the `Vapi` namespace. Bump the package.json template to ^1.2.2,
switch the bootstrap script to `Vapi.CreateAssistantDto` /
`Vapi.UpdateAssistantDto`, and call the new `update({ id, ...body })`
shape. Skill metadata bumped to 1.1.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant