Multiple package updates in a single merge

[outpaddling]

Can the CI tools handle multiple package commits in a single [squash and] merge?
If so, is there anything special that needs to be done in the commit message or otherwise?
I'm thinking of cases where there is an API change in a library that requires a dependent package to be updated. Merging all the updates together is the only way to avoid a brief regression in the dependent package. Otherwise, if someone does a git pull between the commits, they'll experience breakage.

[outpaddling]

After some thought and experimenting, the strategy I'm going to use for now is to import and manually CI-test the packages all into the same test branch one at a time. This makes it easier to check for and address regressions against trunk. Once everything is verified, I'll merge the test branch into trunk, which will trigger another CI build that should produce the same results as the manual builds in the test branch. This way, no regressions should land in trunk and users of trunk will never see an inconsistent tree (all package updates will be merged at once).