docs: clarify private preview SDK access in README#3393
Merged
Conversation
Committed-By-Agent: claude
jar-stripe
marked this pull request as ready for review
June 3, 2026 23:14
jar-stripe
enabled auto-merge (squash)
June 3, 2026 23:14
xavdid
approved these changes
Jun 8, 2026
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
2 participants
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.
Why?
The private preview SDK section previously said "These are invite-only features. Once invited, you can install..." — implying users need an invitation to install the SDK. In reality, anyone can install the
-alpha.XSDK versions. It's the private preview API features that may require separate access approval. This creates unnecessary friction for developers who see "invite-only" and assume they can't even try the SDK.What?
See Also
Similar language is being updated across the other Stripe SDK READMEs for consistency.