A tale of dependencies
One Friday afternoon we got a Slack message from one of our early customers, letting us know that there was an issue with updating our SDK. Apparently, our SDK introduced a new dependency to the code that their team wasn’t able to meet: graphql@16.0.1. This made it impossible for the customer to upgrade to a newer version of our SDK and became a blocker for them.