Repository navigation
Let the npm publish import smoke test load the 0.1.1 build - #1
Merged
Merged
Conversation
…import smoke test (monorepo #22724)
|
In Sazabi, open GitHub integration settings, choose your GitHub connection, then add this repository under Code settings. |
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
Part of ENG-11293. The publish run for 0.1.1 (https://github.com/sazabi/react-native/actions/runs/41945695783) failed in the import smoke test: the stand-in
react-nativemodule lacksNativeModulesandTurboModuleRegistry, and the stand-inreactlacksComponent, all of which the 0.1.1 build imports. This is the same change as monorepo #22724, which fixes the source copy of this workflow; the release pipeline does not sync workflow files here, so it is applied directly.Validation
Merging to
mainreruns the publish on the 0.1.1 release commit already here. The publish step itself also needs the npm trusted publisher for@sazabi/react-nativeto be bound to this repository and workflow.