Smithery is now a part of Arcade.dev! Read more in our announcement here
Upgrade Linear SDK versions and migrate breaking changes. Use when updating to a new SDK version, handling deprecations, or migrating between major Linear API versions. Trigger with phrases like...
Derive the migration from the installed/current SDK diff and live schema instead of assuming every version change repeats the historical 1.x-to-2.x rename.
Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Linear documentation and package metadata. Use Write or Edit only for requested implementation with known target files. Never write credentials, customer content, unrestricted environment output, or unredacted GraphQL variables.
@deprecated, and API changes appear in the changelog with an [API] prefix.@linear/sdk 95.0.0 requiring Node.js >=18.x; recheck before each upgrade.Use a personal API key only for owner-controlled scripts, OAuth with PKCE for user-delegated applications, or an enabled client-credentials grant for approved automation. Personal keys use Authorization: <API_KEY>; OAuth tokens use Authorization: Bearer <ACCESS_TOKEN>. Store credentials server-side in an approved secret manager.
Treat app approval, team access, scope changes, credential creation, rotation, revocation, and production access as owner-approved actions.
Do not create, reveal, rotate, or revoke credentials; authorize an OAuth app; change scopes or team access; create, mutate, archive, or delete workspace data; configure or re-enable webhooks; import or export data; change roles, SCIM, or audit streaming; transmit diagnostics; change paid entitlements; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.
Return the workspace and team scope, auth mode without credential value, files and contracts inspected, exact operation names, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.
| Condition | Response |
|---|---|
| No release evidence | Do not guess migration steps from the version number; inspect the package/schema diff. |
| Node incompatible | Upgrade runtime through its own approved lane or choose a supported SDK version. |
| Deprecated field still works | Schedule removal from the documented notice; do not rely on a non-functioning stub. |
| Live probe differs | Stop rollout, preserve the response contract, and update tests/adapter deliberately. |
Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable.
Input:
current=resolved-lockfile; target=95.0.0; raw-queries=4; deprecations=inventory
Expected handoff:
diff=reviewed; tests=required; rollout=staged; rollback=package-pin
