主要SemVer更新是否应该级联？ [英] Should major SemVer updates cascade?

问题描述

因此， myLibrary引用 anotherLibrary。这两个库都遵循 http://semver.org/

So "myLibrary" references "anotherLibrary". Both libraries follow http://semver.org/

如果我发布了新版本的myLibrary来迫使消费者更新到另一个库的新主版本，则myLibrary的主版本也应该增加吗？

If I release a new version of myLibrary that forces consumers to update to a new major version of anotherLibrary should the major version of myLibrary also increment?

推荐答案

这是在semver的FAQ部分中专门回答的，建议不要突出主要版本。 http://semver.org/#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api

This is specifically answered in the FAQ section of semver, where it is recommended that the major version be not bumped up. http://semver.org/#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api

这篇关于主要SemVer更新是否应该级联？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！