upgrade-stripe

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

13|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/vedang/dotagents --skill upgrade-stripe-vedang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade-stripe
Source: https://github.com/vedang/dotagents/tree/main/specific_skills/upgrade-stripe
Command: npx skills add https://github.com/vedang/dotagents --skill upgrade-stripe-vedang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Upgrading Stripe API versions and SDKs involves navigating breaking changes, version-specific behaviors, and platform differences, and mistakes can break payment integrations in production. ## Core Features & Use Cases - API Version Migration: Explains Stripe's date-based versioning, backward-compatible versus breaking changes, and how to pin or override API versions per language. - SDK Upgrade Guidance: Covers server-side SDKs (Ruby, Python, PHP, Node.js, Java, Go, .NET), Stripe.js evergreen releases, and iOS, Android, and React Native mobile SDKs. - Use Case: You need to move your Node.js integration from API version 2024-12-18.acacia to 2026-06-24.dahlia. Follow the upgrade checklist to review the changelog, update the SDK package, set the apiVersion parameter, and test with the Stripe-Version header before switching your account default. ## Quick Start Ask the agent to walk you through upgrading your Stripe integration to API version 2026-06-24.dahlia, including SDK updates and webhook testing.

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, set the apiVersion parameter in your Stripe client initialization, and test with the Stripe-Version header before changing your account default.

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

Send requests with the Stripe-Version header set to the target version, for example via curl or by setting apiVersion in your client configuration. This lets you validate behavior against the new version while your account default stays unchanged.

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

No. Strongly-typed SDKs use a fixed API version matching the SDK release date, and response objects may not match the strong types if you override it. Instead, upgrade the SDK package itself to target a newer API version.

What Stripe changes are breaking versus backward-compatible?

Backward-compatible changes include new resources, optional parameters, new response properties, and new webhook event types. Breaking changes include field renames or removals, behavioral modifications, and removed endpoints or parameters, all of which require code updates.

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

No. Each Stripe.js major release (Acacia, Basil, Clover, Dahlia) automatically pairs with its corresponding API version, and you cannot override this association. Load a versioned Stripe.js via the script tag or matching npm major version.

Are Stripe mobile SDKs compatible with any backend API version?

Yes. iOS and Android SDKs follow semantic versioning and work with any Stripe API version used on your backend unless documentation specifies otherwise. The React Native SDK uses a 0.x.y scheme where minor version changes can include breaking changes.