upgrade-stripe

github:stripe/ai · first seen 2026-10-31 · installs 74.2K · source · badge

Skill Health 88 (freshness and quality) estimated by backskills

Listed, not yet scored. This skill has no public model test yet. It is in the scoring queue; submitted skills go first, then the most-installed.

Freshness 100 · Quality 75 · Efficacy not yet tested

Version history

2026-11-01T09:00:35+00:00 · sha256 472ec56ccf95

2026-10-31T09:01:00+00:00 · sha256 29920524cb58

Diff at 2026-11-01T09:00:35+00:00

--- previous
+++ current
@@ -12,7 +12,7 @@
 
 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](https://docs.stripe.com/api/versioning.md) 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-10-31. 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.
+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-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.