greenkeeper | : robot : : palm_tree : Real-time automated dependency | Runtime Evironment library

Background

I've just added a greenekeeper.json file to an already existing (and Greenkeeper enabled) repo to account for additional package.json files that were not previously being monitored by Greenkeeper.

greenkeeper.json

I have a large personal software library that I have been working on and is currently working on. Currently, its version is 0.1.0.

It is not mature enough to have a major version of 1. I keep modifying the code and introducing incompatible changes that would merit an increase of the major version number. At the same time, some of my other libraries depend on this library and refer to it by the version number.

If I introduce incompatible changes and don't want to increase the major version from 0 to 1, how should I increment my version number?

The SemVer website is not very clear on that, it just says:

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

Does "anything may change at any time mean" that an exception is made for a major version of 0 and that I can change the y and z numbers however I like?

For instance, if my version is 0.1.0 and I introduce an incompatible change, could the new version with that change be 0.2.0?

What others say

On this site it says:

In fact, the SemVer spec defines that anything starting with “0.” doesn’t have to apply any of the SemVer rules.

Another site also seems to suggest that it is OK to increase the minor version when the major version is 0 and incompatible changes are added:

So you just continue through the 0.x.y range, incrementing y for every backwards-compatible change, and x for every incompatible change.

Is there anything like greenkeeper.io or dependabot.com for VSTS? These solutions will look into the package.json file, compare the current project's version of a dependency against the most recent published version, and propose PR's that are incrementing the dependency to the latest version.

I run travis on multiple version of NodeJS. E.g. 6, 7, 8, 9.

In the build process, I run code coverage and other things.

Is there a way to skip running those script on particular NodeJS?

e.g. code coverage tool only need to be run on one of the build (e.g. the highest version).

That would save some time for me and resources for travis.

For example, I would like to skip before_install, before_script, after_script and after_success on NodeJS 6 and 8 in the .travis.yml below: