Repository navigation
Align Stripe API version pins to 2025-12-15.clover - #3124
Open
hariharapanigrahy wants to merge 1 commit into
Open
hariharapanigrahy wants to merge 1 commit into
hariharapanigrahy wants to merge 1 commit into
Conversation
Several sample paths still used 2020-08-27 (and a few other outdated pins) while Next.js and TypeScript servers already target 2025-12-15.clover. Unify explicit apiVersion / api_version / Stripe.api_version pins so client and server samples request the same contract shape. Evidence: in-repo modern baseline + stripe SDK ^20 clover train. Follow-up: bump to 2026-07-29.dahlia requires coordinated SDK majors.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
2025-12-15.clover.2020-08-27,2020-03-02,2022-11-15,2023-10-16, and2024-06-20while Next.js / TypeScript servers already used2025-12-15.clover.Evidence
payment-element/server/nextjs/lib/stripe.tset al. already pin2025-12-15.clover2020-08-27, 5× clover, plus older pinsstripepackages are^20.x(clover train); latest npmstripe@22.4.0defaults to2026-07-29.dahliaWhy not dahlia yet?
Jumping to
2026-07-29.dahliarequires coordinated SDK majors (stripe^22, matching PHP/Ruby/Python). Suggested follow-up PR.Test plan
Stripe-Version: 2025-12-15.clover