fix: update Podfile.lock after RN upgrade #385
Merged
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
kirillzyusko
added
🍎 iOS
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.
📜 Description
Update
Podfile.lock.💡 Motivation and Context
In #299 I updated RN to
0.73.5. However straight before a merge a new version has been released, and I updated it to0.73.6(but I forgot to remove Pods directory). As a result on CI we were trying to install0.73.6version (without cache) when0.73.5was declared inPodfile.lock.So this is a follow up for #299
📢 Changelog
iOS
Podfile.lock🤔 How Has This Been Tested?
There is only a way to test it on CI 👀
📝 Checklist