Upgrade Stripe

This walks you through upgrading Stripe API versions, SDKs, and Stripe.js without breaking your integration. It covers the difference between dynamically-typed languages where you can set api_version in code versus strongly-typed SDKs where you need to upgrade the whole package. The source material is detailed about testing with Stripe-Version headers before committing and explains why Stripe.js versions auto-pair with specific API versions. Most useful when you're finally dealing with that API upgrade you've been postponing, or when you need to understand why your Ruby code can specify a version but your Java SDK can't. The checklist at the end is genuinely practical.

skills.sh installs: 239
GitHub stars: 1.6K
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add stripe/agent-toolkit --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