So \"myLibrary\" references \"anotherLibrary\". Both libraries follow http://semver.org/
If I release a new version of myLibrary that forces consumers to update to a new
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