Add release candidate logic to publish script #618
Merged
Conversation
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
cbala-stripe
approved these changes
Sep 9, 2025
alanyan-stripe
pushed a commit
to alanyan-stripe/react-stripe-js
that referenced
this pull request
Sep 10, 2025
* Add release candidate logic to publish script
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 & motivation
This PR modifies the
scripts/publishscript to align (via copy/paste) with@stripe/stripe-js. This will allow us to create release candidate for upcoming major versions.The code was copy-pasted from the other publish script and is visibly equivalent to the current script when not in a release candidate other than removing the other preversion logic and removing a redundant github check (as was done on the
stripe-jsscript a while back)