Those aren't manufacturing defects. They are all changes of dependencies that should be made clear in the contract anyways.
I have to admit that i am not too familiar with how Linux versioning works (more of a windows environment guy), but if I buy software that was developed for windows 7, that stops working on windows 10 then it's obviously not a manufacturing defect. That's me changing to OS to a none supported one. I believe that "System Requirements" is a fair section for software to have.
And assuming that i was informed before hand that the software depends on Twilio API version X.Y i won't see those changes as a manufacturing defect either.
In my opinion, manufacturing defects are things such as:
- the software corrupting data during normal operation
- the software behaving differently than specified in the documentation
- the software not handling edge cases correctly
> easy to use extensible API for all SMS providers
Don't ever use that language within your technical/legal documents. It's fine for marketing, but when it comes to specifications always be specific. If you write something like this, but not what Providers/API in particular you are using/offering then don't be surprised if I am annoyed when your software stops working. After all I literally had no way of knowing what you supported, you didn't give me that very specific information.