Amy Egan Thanks for the feedback! Yes, this is something others have also run into. It's expected behavior for now, as you saw in the docs. vercel.com/docs/monorepos#requirements Changing that behavior is more complex than it might seem at first glance, so we don't have an immediate solution. But I shared this thread with the team and I'll keep it open so others can share their experience and suggestions 😃
Amy Egan Also want to share another workaround I've seen. You can build a custom workflow to have more control over exactly what gets deployed and avoid the canceled deployments. There's a basic script template and setup steps for GitHub Actions in this guide: vercel.com/kb/guide/how-can-i-use-github-actions-with-vercel That's obviously a bit more work than the standard automatic deployments. But once you've got it set up it just works. I hope that helps!
Timothy Thanks for the suggestion! I'll probably end up going with GitHub actions for now. I definitely would love to see some work on the skip unaffected deployments feature to be a bit more controlled, especially since polyglot monorepos are more and more popular these days. I do think some more control based on these environments would be welcome.
