2 ms·
That's why for internal projects we switched to using the build number for versioning. Developers rarely get SemVer right, or outright don't care about it. We'v
by oweiler 9y ago
That's why for internal projects we switched to using the build number for versioning. Developers rarely get SemVer right, or outright don't care about it. We've also seen patch versions breaking clients because of some transitive dependency upgrade which was impossible to forsee.
- bunderbunder 9y agoIdeally you shouldn't be changing dependency versions when you're just doing a patch, precisely because it's so hard to predict potential impact when you upgrade a dependency.
- marcodave 9y ago> Ideally you shouldn't be changing dependency versions when you're just doing a patch, what if the patch included updating the (patch) version of a direct dependency? then you don't have much more control over what that direct dependency would bring on