upgrade-stripe

This skill provides comprehensive instructions for maintaining and upgrading Stripe integrations. It covers date-based API versioning, migration strategies for server-side SDKs, and maintaining compatibility across Stripe.js and mobile environments. Developers can use this agent to identify necessary code updates when moving between API versions, understand the difference between backward-compatible and breaking changes, and apply best practices for SDK configuration.

• Detailed walkthroughs for upgrading Stripe API versions, including testing strategies using the Stripe-Version header.

• SDK-specific guidance for dynamically-typed languages like Python, Ruby, PHP, and Node.js versus strongly-typed languages like Java, Go, and .NET.

• Instructions for updating Stripe.js via script tags or npm packages, and managing associated API version pairs.

• Migration support for mobile SDKs on iOS, Android, and React Native, focusing on semantic versioning and backend compatibility.

• Expert advice on checking the API changelog, updating webhook handlers, and handling object ID changes to avoid service interruptions.

• Always verify your integration against the latest recommended API version (2026-04-22.dahlia) unless a specific legacy version is required.

• Use the Stripe-Version header to safely test new API versions in staging or development environments before updating your account default.

• Strongly-typed SDKs require an SDK update to target new API versions, whereas dynamically-typed SDKs allow for global or per-request configuration overrides.

• Always review the Stripe API Changelog for field renames, removals, or behavioral changes that may break existing functionality.

• When migrating to newer Stripe.js major versions, ensure your platform configuration aligns with the predefined pairing requirements for API versions.

• Ensure your database schema supports the updated Stripe object ID lengths and formats to maintain data integrity across API upgrades.