linear-upgrade-migration

# Linear Upgrade Migration ## Overview Safely upgrade `@linear/sdk` versions with zero downtime. The SDK is auto-generated from Linear's GraphQL schema -- major versions can rename fields, change return types, add required parameters, or remove deprecated methods. This skill covers version checking, upgrade procedure, compatibility layers, and rollback. ## Prerequisites - Existing Linear integration with version control (Git) - Test suite covering Linear SDK operations - Understanding of semantic versioning ## Instructions ### Step 1: Check Current vs Latest Version ```bash set -euo pipefail # Current installed version npm list @linear/sdk 2>/dev/null || echo "Not installed" # Latest available npm view @linear/sdk version # All recent versions npm view @linear/sdk versions --json | jq '.[-10:]' ``` ### Step 2: Review Changelog for Breaking Changes ```bash set -euo pipefail # View SDK changelog on GitHub npm view @linear/sdk repository.url # Then check: https://github.com/linear/linear/blob/master/packages/sdk/CHANGELOG.md # Also review Linear's API changelog: # https://linear.app/changelog (filter for API/developer updates) ``` Common breaking changes between major versions: - **Renamed fields**: e.g., `issue.state` property vs lazy relation - **Changed return types**: direct value to paginated connection - **New required parameters**: mutations gaining mandatory fields - **Removed methods**: deprecated methods dropped - **ESM/CJS**: module system changes ### Step 3...