I'm doubting this decision now. Yet it risks flaky pipelines but there's also the danger of false negatives since it may be that the new PR is the culprit for introducing a regression against the latest deps, and that it gets merged-in without otherwise being caught.

The cron schedule helps catch issues quickly, hopefully before PRs are made. On balance, I think it would be better to enable the max-deps CI worker even for PRs.