Fix update_upstream to run pod update in all sub-packages #863
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
Any package that has an example or integration_test_app needs to have pod update run in order for their lock files to be updated properly.
fuzzybinary
force-pushed
the
jward/flutter-update-fix
branch
from
8a8e6ea to
a61beca
Compare
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.
What and why?
Now that the Flutter plugin is split into multiple packages, we need to make sure to run
pod updatein all the sub-examples and integration test apps to make sure they all update their Podfile.lock files. This runs through all the packages inpackagesand updates all of them (including the main plugin).How?
This is based on #862 and needs to go in after it.
Review checklist
Custom CI job configuration (optional)