We were using a fork we customuzed of an open source package (we will merge our additions but the team wants us to wait until they’re done with a major revision). At some point another upstream package made a fundamental change that broke everything. So we learned the hard way to have upper bounds on all required package version numbers lol. That was such a pain to investigate.
We were using a fork we customuzed of an open source package (we will merge our additions but the team wants us to wait until they’re done with a major revision). At some point another upstream package made a fundamental change that broke everything. So we learned the hard way to have upper bounds on all required package version numbers lol. That was such a pain to investigate.
Lol, sounds like the work I would do at my job. But absolutely! This is why there should always be a >= and <= version requirement on dependencies.
Dooown with needless updates