When you upgrade to Stripe API version 2026-09-30.endive (or an SDK major that pins it), Reserve Release objects report reason hold_expired instead of bulk_hold_expiry
Took effect · Stripe API 2026-09-30.endive — Reserve Release reason bulk_hold_expiry renamed to hold_expired
Reviewed against the vendor source on Oct 2, 2026 (AI-assisted review). Key facts are re-checked against the source daily.
What changes
Code that matches the reason property against bulk_hold_expiry stops matching without an error. reason is an open enum, so Stripe also asks integrations to handle unrecognized values.
Silent: No error. Behavior, results, or cost change quietly.
What to do
Before moving to 2026-09-30.endive, match Reserve Release reason against hold_expired instead of bulk_hold_expiry, and handle unknown values.
Counts only in files that mention stripe; repos that depend on stripe 16.x (pypi) or stripe 23.x (npm) or stripe 20.x (rubygems) or github.com/stripe/stripe-go/v87 87.x (go) or stripe/stripe-php 22.x (packagist); or repos that mention 0.endive or 1.endive or 2.endive or 3.endive or 4.endive or 5.endive or 6.endive or 7.endive or 8.endive or 9.endive or stripe==16 or stripe>=16 or stripe~=16 or stripe = "^16 or stripe = "~16 or stripe = ">=16 or stripe = "==16 or stripe = "16 or "stripe": "^23 or "stripe": "~23 or "stripe": "23 or stripe@^23 or stripe@23 or stripe-go/v87 or stripe (20. or gem 'stripe', '~> 20 or gem "stripe", "~> 20 or stripe-java:34. or Stripe.net" Version="53 or "stripe/stripe-php": "^22 or "stripe/stripe-php": "~22 or "stripe/stripe-php": "22 or stripe@npm:^23 or stripe@npm:23 (including dependency manifests).