semver.io is flakey - wrong node version #43
Description
When I was setting up a new Heroku app today it was installed with node version 0.10.21 (which totally does not work with the latest Meteor version).
----> Fetching custom git buildpack... done
-----> Meteor app app detected
-----> Resolving engine versions
No version of Node.js specified in nodeversion, using '0.10.26'
Using Node.js version: 0.10.21
-----> Fetching Node.js binaries
- downloading and extracting node from http://s3pository.heroku.com/node/v0.10.21/node-v0.10.21-linux-x64.tar.gzSo I investigated it a bit and found that semver.io changes its response with each other request. I just ran curl multiple times from the command line and got this:
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.21
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.21
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.26
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.26
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.21
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.21
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.21
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.26
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.26
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.21
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.26
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.26
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.26
$ curl --silent --get --data-urlencode "range=0.10.26" https://semver.io/node/resolve
0.10.21Probably not a good thing to continue using samver. Working on a fix, will make a Pull Request shortly.