[RN][CI] Setup release publishing flow#248
Merged
kieran-osgood-shopify merged 1 commit intoJun 2, 2026
Merged
Conversation
fix: prepare React Native npm publish workflow chore: simplify release workflow modes
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
kiftio
approved these changes
Jun 2, 2026
11 tasks
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.

What?
React Nativeto workflow_dispatch for releasesreact-native/X.Y.Ztagreact-native/namespace.Theres some scripts added to give us the ability to test tarbals of the release build against expo and react-native community cli installs, as well as with npm / yarn / bun / pnpm.
I also fixed some output on the release plan

Other
In order to produce react-native
4.0.0-alpha.1I needed to update podspec and gradle to point to the swift/android4.0.0-alpha.1versions published last weekWe have this awkward process for gradle, where the android sdk has to build and publish to
mavenLocalfor local dev, this is gated behind theUSE_LOCAL_SDKflagThis could fail silently if mavenLocal didn't have a 4.0.0-alpha.1 version, so I added an exclusiveContent filter which ensures the checkout-kit library, when the
USE_LOCAL_SDKflag is true, will fail to build, ensuring we don't accidentally false positive test against a published SDK in maven.