upgrade-stripe

Guides upgrading Stripe API versions, server-side SDKs, Stripe.js, and mobile SDKs.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/divinaarmuela/Content --skill upgrade-stripe-divinaarmuela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade-stripe
Source: https://github.com/divinaarmuela/Content/tree/main/.claude/skills/upgrade-stripe
Command: npx skills add https://github.com/divinaarmuela/Content --skill upgrade-stripe-divinaarmuela

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about upgrade-stripe

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

FAQPage Schema
How do I upgrade my Stripe API version?

Review the API changelog for changes between your current and target versions, update your server-side SDK package, and set the apiVersion parameter in your Stripe client initialization. Test against the new version using the Stripe-Version header before switching your default.

How do I test a new Stripe API version without changing my default?

Use the Stripe-Version header in API requests or set the apiVersion option in your SDK client to test against a specific version. This lets you validate behavior without modifying your account's default API version.

Should I set an API version for Java, Go, or .NET Stripe SDKs?

No. Strongly-typed SDKs use a fixed API version matching the SDK release date. Setting a different version risks response objects not matching the SDK's strong types, so upgrade the SDK package itself instead.

What counts as a breaking change in Stripe API versions?

Breaking changes include field renames or removals, behavioral modifications, and removed endpoints or parameters. Backward-compatible changes like new resources, optional parameters, and new response properties do not require code updates.

Does Stripe.js versioning work independently from the API version?

No. Each Stripe.js major version (Acacia, Basil, Clover, Dahlia) automatically pairs with its corresponding API version, and this association cannot be overridden. Upgrading Stripe.js also changes the API version it uses.

Are Stripe mobile SDKs compatible with any backend API version?

Yes. iOS and Android SDKs work with any Stripe API version used on your backend unless documentation specifies otherwise. Mobile SDKs follow semantic versioning, while the React Native SDK uses a 0.x.y schema where minor changes may break compatibility.