Thanks for the idea, it really makes sense, so we’re starting to evaluate how to implement this.Björn Schneider supported this idea ·Björn Schneider commented
You might use comments along with the version definitions, like requires.io (Python) does. In pip's requirements.txt you would write something like:
Django==1.8.9 # gn.version>1.8.0,<1.9.0 gn.expires=2018-04-01
...which means "pin it to a version between 1.8.0 and 1.9.0" (that's a long term support version), but warn after April, 1st 2018 (when the support runs out).
Similar schould work for other build systems, unfortunately not for npm - JSON files can't contain comments. Here you'd need to use an own sub-key, e.g.:
...which would warn after July, 1st 2018 if you still use a 2.7 version of wepack.
That's for the two packaging systems/languages I use and need support for. But I guess there are similar options for the other ones supported by Gemnasium.