What problem does it solve? Upgrading Stripe API versions and SDKs involves breaking changes, version pairing rules, and testing requirements that are easy to miss, risking failed payments or broken webhook handlers. ## Core Features & Use Cases - Version Upgrade Guidance: Explains Stripe's date-based API versioning (e.g., 2026-07-29.dahlia) and distinguishes backward-compatible changes from breaking changes. - Multi-Platform Coverage: Covers server-side SDKs (Python, Ruby, Node.js, Java, Go, .NET), Stripe.js evergreen releases, and iOS/Android/React Native mobile SDKs. - Upgrade Checklist & Testing: Provides a step-by-step checklist and shows how to test new versions safely using the Stripe-Version header. - Use Case: Your backend pins an old Stripe API version and you need to migrate to 2026-07-29.dahlia. Use this Skill to review breaking changes, update the apiVersion parameter, and validate webhooks before switching. ## Quick Start Help me upgrade my Stripe integration to API version 2026-07-29.dahlia and review what breaking changes affect my code.