>But their repo, their rules, their business decisions
Was it not BSD or GPL or some similar license? If so someone could just fork it while ignoring their rules and business decisions (as long as at least one other person had the code I guess).
Was it not BSD or GPL or some similar license? If so someone could just fork it while ignoring their rules and business decisions (as long as at least one other person had the code I guess).
Maybe you’re a developer who can keep account of multiple layers, or all layers in your stack. If so that’s great. But we’re all limited to varying degrees and there’s only so much one can do. Really, you need to find reliable partners who can own some of that complexity for you.
In OPs case, they picked a partner that was not reliable. They paid for it with more maintenance. But this is what you get with open source. You can get it for free and you can set it up fast because you don’t need to negotiate contracts, but your dependencies are under no obligation to support your use cases.
But yeah I get it, too much of a pain, too unrealistic, etc.
Of course, open source software is not the only thing at risk of this, seems like most modern software gives you little control over what version you use.