Date the Stripe changelog entry by version rather than by "current"

"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 <[email protected]> Claude-Session: https://claude.ai/code/session_01D9acV1mHktGAb1uyvNmrR2
2026-08-24 23:17:33 -03:00
parent e2da45a1b0
commit 88a8d0ae5c
1 changed files with 1 additions and 1 deletions
@@ -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]