Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fcakyon/upgrade-stripe
Guide for upgrading Stripe API versions and SDKs
Passed 21 of 22 test cases with the skill, and 9 of 22 without it.
and 22 more in the full report
12 fixed9 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We load Stripe.js on our checkout page via npm @stripe/stripe-js. We want to configure Stripe.js to use API version 2024-12-18.acacia while using the Dahlia bundle script. Can we pass apiVersion in the Stripe.js options?
| Checked | Without skill | With skill |
|---|---|---|
| States that Stripe.js API version cannot be independently overridden in options. | Missed | Passed |
| Explains that each Stripe.js release automatically pairs with its corresponding API version. | Missed | Passed |
The instructions your model reads when the skill loads.
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-08-26.dahlia. This value is only a snapshot from the last time this skill was generated, on 2026-10-01. 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.
Before making changes, compare the target with each API version the integration pins: client configuration, per-request overrides, and webhook endpoints. Unless the user explicitly asks for it, don’t move any pin to an older version or a stable pin to a preview version. If a pin already matches the target, report it as unchanged. State the selected target and its source. If live verification fails or is unavailable, say that the latest version remains unverified, and don’t claim the integration is on the latest version.
When reviewing webhook endpoints and event destinations, distinguish snapshot events from thin events. Thin event payloads are unversioned, so they don’t need to be upgraded when you change your API version. API calls that retrieve the full event or related resource remain versioned.
For SDKs that support explicit API version overrides, use the selected target in client configuration and per-request overrides. Use it in curl Stripe-Version test headers, too. Replace bundled API versions shown in those examples with the selected target before copying or running them. For Java, Go, and .NET, select an SDK release that targets the selected API version instead of overriding the SDK’s fixed version. Preview targets need the matching beta SDK release in every language; see SDK versioning.
Stripe uses date-based API versions (e.g., 2026-08-26.dahlia, 2025-08-27.basil, 2024-12-18.acacia). Your account’s API version determines request/response behavior.
Starting with the 2024-09-30.acacia release, Stripe releases new API versions monthly with no breaking changes. Twice a year, a new major release (for example, Basil) starts with an API version containing breaking changes. You can safely upgrade to any monthly release without updating your code.
Backward-Compatible Changes (don’t require code updates):
Breaking Changes (require code updates):
Review the API changelog for all changes between versions. See API upgrades for the full upgrade guide.
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.