What problem does it solve? Upgrading Stripe API versions and SDKs involves navigating breaking changes, version-specific behaviors, and platform differences across server-side, web, and mobile integrations, which can cause integration failures if done incorrectly. ## 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 versioning (Acacia, Basil, Clover, Dahlia) and semantic versioning for iOS, Android, and React Native SDKs. - Use Case: You need to move your Node.js integration from API version 2024-12-18.acacia to 2026-07-29.dahlia. Follow the upgrade checklist to update the SDK package, set the apiVersion parameter, test with the Stripe-Version header, and update webhook handlers. ## Quick Start Ask the assistant to help upgrade your Stripe integration to API version 2026-07-29.dahlia and review the breaking changes that apply to your codebase.