fix: remove merge conflict from expo54 fix#339
Closed
kieran-osgood-shopify wants to merge 1 commit intokieran-osgood/release/3.3.2from
Closed
fix: remove merge conflict from expo54 fix#339kieran-osgood-shopify wants to merge 1 commit intokieran-osgood/release/3.3.2from
kieran-osgood-shopify wants to merge 1 commit intokieran-osgood/release/3.3.2from
Conversation
Coverage Report
|
kieran-osgood-shopify
force-pushed
the
kieran-osgood/release/3.3.3
branch
from
e7e97e6 to
dfe6b4d
Compare
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
1 participant
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 changes are you making?
There was a bad merge conflict in the latest patch that meant the podspec still had the old dependencies
PR Checklist
Important
Releasing a new version of the kit?
package.jsonfile.Tip
See the Contributing documentation for instructions on how to publish a new version of the library.