[Release Tooling] Re-order pod manifest #9783
Merged
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.
Context
FirebaseCoreExtension
depends onFirebaseCore
, which depends onFirebaseCoreInternal
so they so should be pushed in reverse orderFirebaseCore*
pods and I have them being pushed afterFirebaseCore*
pods. I think this should a buffer for theFirebaseCore*
to be fully published by the time the product pods start being pushed#no-changelog