Merge 21.6 code freeze into trunk with conflicts resolutions
#19973
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.
See #19964 description.
We got conflicts on
Podfile.lockchecksum because bothtrunkandrelease/21.6changedPodfile.trunkwith b146b82release/21.6with 018a5e1I resolved the conflicts by re-running
bundle exec pod installto generated a new checksum field.Since this PR differs from #19964 only in fixing the
Podfile.lockchecksum conflict, I'm going to consider the approval on #19964 as approval for this one too, and admin merge.