Yes, you will need to merge your dependency PRs before the PR itself. Otherwise the post-merge check will fail but will recover once the dependencies have been updated. I don’t really think there is any way around that.

Instead of doing this in the regular checks that are triggered on the PR events we could make this triggered by leaving a comment on the PR.
This way you can trigger it manually and get feedback if it works. Then merge the PRs in your deps. Once they are merged you can run the normal PR checks.
Would that work?

Instead of doing this in the regular checks that are triggered on the PR events we could make this triggered by leaving a comment on the PR.
This way you can trigger it manually and get feedback if it works. Then merge the PRs in your deps. Once they are merged you can run the normal PR checks.
Would that work?

No, that doesn’t work. swiftlang/swift-syntax#2859, for example, introduces a breaking swift-syntax change that needs a corresponding update in swift-format, since swift-format is also in the toolchain (in this case, that changes is done by swiftlang/swift-format#866). Thus, we need to be able to get both the swift-syntax and the swift-format PR into a green CI state at the same time so that the Merge pull request button can be hit on both of them at (roughly) the same time. This is how cross-PR testing works in then Jenkins-based Swift CI for toolchain repos at the moment (https://github.com/swiftlang/swift/blob/main/docs/ContinuousIntegration.md#cross-repository-testing).