sentry-upgrade-migration

# Sentry Upgrade Migration Detect installed Sentry SDK versions, identify breaking API changes, apply automated codemods, and verify the upgrade succeeds with test events and traces. ## Current State !`npm list 2>/dev/null | command grep @sentry || echo 'No npm Sentry packages found'` !`pip show sentry-sdk 2>/dev/null | command grep -E '^(Name|Version)' || echo 'No Python sentry-sdk found'` !`node --version 2>/dev/null || echo 'Node.js not available'` ## Overview Sentry SDK upgrades require careful handling of breaking API changes. The v7 to v8 JavaScript migration is the most impactful, removing the Hub pattern, replacing Transaction/Span APIs with `startSpan()`, converting class-based integrations to functions, and requiring ESM-first initialization. Python SDK v1 to v2 similarly replaces `configure_scope()` with `get_current_scope()`. This skill automates version detection, runs the official `@sentry/migr8` codemod, applies manual fixes for patterns the codemod misses, and validates the upgrade with test events. ## Prerequisites - Current Sentry SDK version identified (run DCI above) - Target version changelog reviewed - Non-production environment for testing upgrades - All `@sentry/*` packages at the same major version before starting - Node.js >= 18.19.0 or >= 20.6.0 for SDK v8 (ESM support required) ## Instructions ### Step 1. Identify Current SDK Version and Scan for Deprecated APIs ```bash # JavaScript: list all Sentry packages and their versions npm ls 2>/d...