Skip to content

chore(deps): upgrade @linqapp/sdk to ^0.31.0#40

Open
jflayhart wants to merge 1 commit into
mainfrom
bump-sdk-0.31
Open

chore(deps): upgrade @linqapp/sdk to ^0.31.0#40
jflayhart wants to merge 1 commit into
mainfrom
bump-sdk-0.31

Conversation

@jflayhart

Copy link
Copy Markdown
Collaborator

The CLI pinned @linqapp/sdk at ^0.15.1 — sixteen minor versions behind 0.31.0. That predates the SDK's webhooks resource entirely, so client.webhooks.unwrap() (its Standard Webhooks verification helper) was not reachable from the CLI at all.

Dependency bump only. No behaviour change.

Verification

  • tsc --noEmit clean
  • npm run build clean
  • 172 tests pass across 41 files
  • All 23 SDK call sites (chats.*, messages.*, attachments.*, phoneNumbers.*, webhookSubscriptions.*, webhookEvents.*) typecheck unchanged

The SDK is Stainless-generated and the intervening releases were almost entirely additive, which is why a jump this large lands clean.

Why it is split out

Two follow-ups build on this and are easier to review separately:

  • webhook-standard-signatures — make webhooks listen --forward-to emit Standard Webhooks headers so local development matches production
  • login-headless-token — stop login --token prompting without a TTY

🤖 Generated with Claude Code

https://claude.ai/code/session_01L3QhRZE6nKoGLGNhzUkmmF

The CLI pinned ^0.15.1, sixteen minor versions behind. That predates the
webhook resource entirely, so `client.webhooks.unwrap()` — the SDK's Standard
Webhooks verification helper — was not reachable from the CLI at all.

This is the dependency bump only, no behaviour change. Verified: tsc --noEmit
clean, build clean, 172 tests pass across 41 files, all 23 SDK call sites
typecheck unchanged.

Adopting Standard Webhooks in `webhooks listen --forward-to` follows separately
so the version bump can be reviewed on its own.
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.

2 participants