From 88a8d0ae5c57b595b6a8e79bd20e562e33fe4add Mon Sep 17 00:00:00 2001 From: James Griffin Date: Mon, 24 Aug 2026 23:17:33 -0300 Subject: [PATCH] Date the Stripe changelog entry by version rather than by "current" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "the current Stripe library" is only true until Stripe ships the next major. A changelog is read long after the release it describes, so name the versions — 17 to 21, API version 2026-07-29.dahlia — and let those date the entry. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01D9acV1mHktGAb1uyvNmrR2 --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index eef10e3..72d6477 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -14,7 +14,7 @@ each change under the current top section as you work. ## [1.5.5] ### Changed -- **Payments now run on the current Stripe library.** The plugin had fallen four major versions behind Stripe's PHP SDK, which also meant it was asking Stripe to behave like an older version of its API. Taking a card payment and handling a webhook work exactly as before — the same charge is raised, the same events are honoured, and a forged webhook is still rejected — but the plugin now speaks Stripe's current API version, so later payment work does not have to clear this upgrade first. Nothing to do on your side. +- **Payments moved up to version 21 of Stripe's PHP library**, from version 17. Being four major versions behind also meant asking Stripe to behave like an older version of its API; the plugin now uses API version `2026-07-29.dahlia`. Taking a card payment and handling a webhook are unchanged — the same charge is raised, the same events are honoured, and a forged webhook is still rejected. Nothing to do on your side. ## [1.5.4]