[RN]: use published artifacts for RN native builds/tests#227
Merged
kieran-osgood-shopify merged 2 commits intoMay 29, 2026
Merged
Conversation
11 tasks
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced May 28, 2026
React Native — Coverage Report
|
kieran-osgood-shopify
changed the base branch from
kieran-osgood/release-workflow/react-native-publish
to
graphite-base/227
kieran-osgood-shopify
force-pushed
the
kieran-osgood/release-workflow/rn-native-sdk-versions
branch
from
52e5847 to
700a4a1
Compare
kieran-osgood-shopify
force-pushed
the
graphite-base/227
branch
from
4d22b7f to
5668389
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/release-workflow/rn-native-sdk-versions
branch
from
700a4a1 to
6601e20
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/release-workflow/rn-native-sdk-versions
branch
from
6601e20 to
6490780
Compare
kieran-osgood-shopify
force-pushed
the
kieran-osgood/release-workflow/rn-native-sdk-versions
branch
from
6490780 to
39316f7
Compare
kieran-osgood-shopify
changed the title
kieran-osgood-shopify
changed the title
kieran-osgood-shopify
changed the title
kieran-osgood-shopify
force-pushed
the
kieran-osgood/release-workflow/rn-native-sdk-versions
branch
from
023cd15 to
7dc139f
Compare
kiftio
reviewed
May 29, 2026
| } | ||
|
|
||
|
|
||
| def useLocalSdk = (System.getenv("USE_LOCAL_SDK") ?: "0") == "1" |
Contributor
There was a problem hiding this comment.
Is it worth adding this to dev.yml commands?
Probably the best default to use for local dev?
Contributor
Author
There was a problem hiding this comment.
It is part of the dev.yml commands
dev rn android --local will give you local maven
By default I think local being false is safer and less confusing
Most react-native code will want writing/integrating against the released maven/cocoapods to match local with CI
The --local flag is an opt in to the workflow of "I'm working on a swift/android change and I want to test in react-native before releasing" e.g. what we did with prototype/development and during this migration
I don't think this is the default case though, and can be slightly more confusing / trip people up
kiftio
approved these changes
May 29, 2026
Contributor
Author
Merge activity
|
kieran-osgood-shopify
deleted the
kieran-osgood/release-workflow/rn-native-sdk-versions
branch
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
Last week we published version 4.0.0-alpha.1 under the new namespace
With this, we have a version that we can statically point to in our configs, removing the need to have --local runs on CI, which integrates/validates against the wrong build artifact for an actual production release
The USE_LOCAL_SDK environment variable and --local flag will still exist for local development but we no longer run them on CI
This safely guards our releases, and brings back the natural flow of:
develop native sdk -> release native sdk -> develop react native sdk -> release react native sdk
Except you also have the ability to test local dev, meaning you can develop react native at the same time, but when it comes to publishing you have to hold off that graphite stack
Other
I also centralised the native SDK version keys the react-native module depends on in the package.json and pull these programmatically at build time in gradle/ruby.
This simplifies maintenance as we only have to manage the package json to update the version now
Before you merge
Important
platforms/swift/README.mdand/orplatforms/android/README.md)Releasing a new Swift version?
ShopifyCheckoutKit.podspecplatforms/swift/Sources/ShopifyCheckoutKit/ShopifyCheckoutKit.swiftplatforms/swift/CHANGELOG.mdplatforms/swift/README.md(major version only)Releasing a new Android version?
versionNameinplatforms/android/lib/build.gradleplatforms/android/CHANGELOG.mdplatforms/android/README.mdTip
See the Contributing documentation for the full release process per platform.