Actual binary ?

Check out http://www.espruino.com/binaries/git/com­mit_date/

The date on espruino.com/binaries/git/commits/ is the date at which the files were built - which is not the date that the commit was made. If I push many commits in a short period of time, the server starts building the newest commit first - which hopefully explains the issues.

In the version number 1v81.XXX, XXX is the commits since the last release - so if I have some code that I have been working on that is on a Git branch, that can unfortunately have a totally different set of numbers to the ones on the master branch.

Basically if you want to be 100% sure of the latest (and what it is):

• Go to https://github.com/espruino/Espruino
  
• Click on where it says Latest commit abcdef
  
• On the new page it'll say commit 471b8e15ff69f6eaade638b74e3e17f20a3e16b5­ or similar (it also shows what that commit actually was)
  
• copy that number, and use it in the URL, like http://www.espruino.com/binaries/git/com­mits/471b8e15ff69f6eaade638b74e3e17f20a3­e16b5/
  
  

Otherwise you can choose the latest from http://www.espruino.com/binaries/git/com­mit_date/?C=N;O=D - but it's possible you might pick up a later commit that's not on the main git branch.

I guess I should really add a symlink like http://www.espruino.com/binaries/git/lat­est?