What problem does it solve? Upgrading Stripe API versions and SDKs involves breaking changes, version pairing rules, and platform-specific constraints that are easy to get wrong, risking failed payments or broken webhook handlers. ## Core Features & Use Cases - API Version Migration: Explains backward-compatible versus breaking changes and how to pin or override API versions in Ruby, Python, PHP, Node.js, Java, Go, and .NET. - Stripe.js and Mobile SDK Guidance: Covers Stripe.js evergreen releases (Acacia, Basil, Dahlia), npm versioning, and semantic versioning for iOS, Android, and React Native SDKs. - Safe Testing Workflow: Shows how to test a new API version using the Stripe-Version header before changing account defaults. - Use Case: Your Node.js integration pins an old API version and you need to move to 2026-07-29.dahlia. Follow the upgrade checklist to update the SDK, set apiVersion explicitly, test webhooks, and verify response handling. ## Quick Start Ask the assistant to walk you through upgrading your Stripe integration to the latest API version using the upgrade checklist.