Fix incremental installation when dependent pod resources change #11568
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.
Fixes #11567: for projects using
incremental_installation: true
, consuming pods were not updated when their dependencies add/rename/removeresource_bundle
s. WhenSomePodWithResources
updates a resource bundle in its podspec, there should be a corresponding update toConsumingPod
in theConsumingPod-resources.sh
build script:Notable changes:
RESOURCES
for dependencies (if applicable). This ensures the{name}-resource.sh
script is regenerated when dependencies change bundled resources.