|
Revision tags: 1.21.0-1, 1.21.0, 1.20.0-1, 1.20.0, 1.19.0-1, 1.19.0, 1.18.0-1, 1.18.0, 1.17.0-1, 1.17.0, 1.16.0-1, 1.16.0, 1.15.0-1, 1.15.0, 1.14.0-1, 1.14.0, 1.13.0-1, 1.13.0, 1.12.0-1, 1.12.0, 1.11.0-2, 1.11.0-1, 1.11.0, 1.10.0-2, 1.10.0-1, 1.10.0, 1.9.0-1, 1.9.0, 1.8.0-1, 1.8.0 |
|
| #
968:dd79860ee5b9 |
| 27-Feb-2019 |
Valentin Bartenev |
Added trailing zero to version string.
While it looks nicer without zero 3-rd version number, this should
improve interoperability. Version string can be parsed or used for
sorting. And it is easi
Added trailing zero to version string.
While it looks nicer without zero 3-rd version number, this should
improve interoperability. Version string can be parsed or used for
sorting. And it is easier to handle and less confusing when there
is constant number of version parts.
Moreover, NPM also expects version format with 3 parts.
So ".0" has already been used in Node.js module version.
show more ...
|
| #
953:00d8049418cf |
| 22-Feb-2019 |
Alexander Borisov |
Improvement and unification of version processing in build scripts.
This also eliminates expressions that incompatible with BSD make, thus fixing
installation of Node.js module on FreeBSD (broken by
Improvement and unification of version processing in build scripts.
This also eliminates expressions that incompatible with BSD make, thus fixing
installation of Node.js module on FreeBSD (broken by dace60fc4926).
show more ...
|
|
Revision tags: 1.7.1-1, 1.7.1, 1.7-1, 1.7 |
|
| #
878:8867c1c7c2bf |
| 19-Dec-2018 |
Alexander Borisov |
Node.js: added check for libunit version at compile time.
|
|
Revision tags: 1.6-1, 1.6, 1.5-1, 1.5 |
|
| #
816:e92e58984512 |
| 23-Oct-2018 |
Alexander Borisov |
Added ability to publish Node.js module.
|