sentry-sdk-upgrade

Upgrade Sentry JavaScript SDK across major versions with migration steps.

246|29|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/getsentry/sentry-for-ai --skill sentry-sdk-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-sdk-upgrade
Source: https://github.com/getsentry/sentry-for-ai/tree/main/skills/sentry-sdk-upgrade
Command: npx skills add https://github.com/getsentry/sentry-for-ai --skill sentry-sdk-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade the Sentry JavaScript SDK across major versions, reducing manual migration effort and preventing breaking changes after version bumps.

Core Features & Use Cases

  • Detect current Sentry SDK version and target version.
  • Generate a migration path with actionable steps and optional auto-fixes for common API changes.
  • Provide framework- and project-specific guidance, including Next.js, Express, and NestJS patterns.

Quick Start

Upgrade the Sentry SDK in your project by instructing the AI to perform a v7→v8 upgrade first, then proceed to v8→v9 if needed.

Frequently Asked Questions about sentry-sdk-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade the Sentry JavaScript SDK from v7 to v8?

To upgrade the Sentry SDK from v7 to v8, you need a migration path that handles package imports, API renames, and config changes. This process provides actionable steps and optional auto-fixes for common breaking changes.

What breaking changes occur when bumping the Sentry SDK major version?

Bumping the Sentry SDK major version introduces breaking changes to package imports, API names, and configuration structures. Migration requires detecting the current version and applying framework-specific guidance to resolve these API modifications.

Does the Sentry SDK migration support Next.js and NestJS frameworks?

Yes, Sentry SDK migration provides framework-specific guidance for Next.js, Express, and NestJS patterns. It ensures that version bump procedures align with the specific integration requirements of these JavaScript frameworks.

What is the best way to handle Sentry SDK package import updates after a version bump?

The best way to handle Sentry SDK package import updates is to generate a structured migration path that identifies target version changes and applies optional auto-fixes to resolve modified import statements.

Can I skip directly to v9 when upgrading the Sentry SDK from v7?

You should upgrade the Sentry SDK sequentially by performing a v7 to v8 upgrade first, then proceeding to v8 to v9. This step-by-step migration ensures all intermediate API renames and config changes are properly addressed.

Why does my Sentry SDK version bump fail in my Node application?

A Sentry SDK version bump fails when breaking changes in package imports, API renames, or configuration modifications are not resolved. Applying framework-specific migration guidance and auto-fixes for Node projects prevents these errors.