semantic-versioning

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 major version of anotherLibrary should the major version of myLibrary also increment? 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 It really depends on if the public API of the main library changes. I tend to treat libraries as a black box. I don't need

Now that npm publish -f is deprecated, is there a workaround or a package that makes it possible to overwrite a target version after it's been published? I know about semver ; I still want npm publish -f . someone said this on npm's github issue: @nmrony You cannot overwrite previously-published packages anymore (since February 2014, if I recall correctly). https://github.com/npm/npm/issues/8305#issuecomment-236412989 This will probably not be viable but there's an overkill method npm unpublish --force - will delete your entire project wait 24 hours npm publish You can unpublish a specific

Here is the behavior I'm trying to achieve in AppVeyor Build the code (stamp AssemblyInfo with 1.2.3.{build} ) Test the code Create the nuget package if the tests passed Publish the beta package if the package created successfully ( 1.2.3-beta-{build} ) Also make the package available in artifacts. Ideally when publishing a nuget package it would be published as prerelease. In NuGet, this is done by adding alpha characters to the end of the package version. It is also considered bad practice to overwrite an existing package (indeed, many nuget implementations do not allow this). AppVeyor does

Trying to explain the importance of semantic versioning to a friend, I faced the following dilemma. Let's say we have library libfoo , version 1.2.3 that exposes the following function: def foo(x, y): """ Compute the sum of the operands. :param x: The first argument. :param y: The second argument. :returns: The sum of `x` and `y`. """ return x + y Now assume that this function and its documentation change to: def foo(a, b): """ Compute the sum of the operands. :param a: The first argument. :param b: The second argument. :returns: The sum of `a` and `b`. """ return a + b My first impression was