Upgrade Stripe

Stripe's versioning system is messier than it looks at first glance because different SDKs handle versions differently. This guide walks you through the whole landscape: dynamically-typed languages like Python and Node let you set the API version per request, but strongly-typed ones like Java bake it into the SDK release. Stripe.js has its own evergreen model with named releases (Acacia, Basil, Dahlia) that auto-pair with API versions. Mobile SDKs follow semantic versioning but don't care what API version your backend uses. The checklist and testing tips are solid, especially the reminder to test with the Stripe-Version header before committing. Worth keeping around if you maintain integrations across multiple platforms.

skills.sh installs: 10.9K
GitHub stars: 2.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add stripe/ai --skill upgrade-stripe --agent claude-code

Installs into .claude/skills of the current project.

Files

Upgrading Stripe Versions

Choose a target API version

If the user specifies a target API version, use it. Otherwise, look up the current version on docs.stripe.com with any documentation or web tool available to you, for example stripe docs /api/versioning with the Stripe CLI. The API versioning page states it in the sentence that begins “The current version is”.

Bundled fallback API version: 2026-10-28.endive. This value is only a snapshot from the last time this skill was generated, on 2026-11-14. Version identifiers start with their release date in YYYY-MM-DD format and new stable versions are released monthly, so a fallback version dated more than a month ago is probably stale. Use it only when you can’t reach docs.stripe.com. Never guess about a newer version number.

SKILL.md on GitHub