ci(react-native): patch static fixtures to fix boost download url #2280
Conversation
This file contains 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
yousif-bugsnag
force-pushed
the
rn-fixture-boost-patch
branch
from
a9115f9 to
5f2ffd7
Compare
gingerbenw
approved these changes
Jan 10, 2025
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.
Goal
Fixes failing RN test fixture builds (RN v0.66-v0.69) that began failing due to an error when installing the boost pod.
It looks like this is a recurrence of an old upstream issue with the jfrog distribution of the boost pod that has been fixed in more recent versions of React Native (see facebook/react-native#42180)
Design
As per the linked issue above, installed
patch-packageinto the affected test fixtures and applied a patch to install boost from the boost archive url rather than jfrog.Testing
Covered by a full CI run