It isn't Construct's fault by itself, the issue arises when I have a project with different people, and each of them turn out to have a different version, because for some reason it got updated to some, but not to all.
As long as we stayed in the same version, absolutely nothing bad happened, but as soon as different versions got involved, which happened in an older project of mine, everything became a mess. Different branches that when merged got the project corrupted, and I had to edit .json files everyday to make it work. I frequently use custom plugins I've written or modified, which get broken as well. That's why for the next big project I made sure to stay on the same version, no external third party stuff (which includes not using an unofficial desktop launcher), and this makes it impossible.
Lots have given up from using Github, and it's not Construct's fault AT ALL! If you know what you're doing, and solve conflicts correctly, all of the issues can be solved, always. But forcing updates into my team is absolutely unnecesary.
The only thing that was keeping me in was having a workflow where I could control in which version everyone is, until I'm ready to upgrade if it's necessary. I'm not going to abuse this in any way, as I love every feature you all add, and I've never reported a bug without making sure I was on the latest version. I'm not asking for a "skip version" button on start that would lead to people reporting the same bugs again and again, but an advanced option for cases like these. I hope it's more clear now, I'm trying my best to explain this.