Commit 1bac49c
committed
fix: use dash as separate in package version
The Linux package build was using a dot to separate the "release base" and
the "patch" values when updating the "version" property in the package.json
file. This could result in a version like "2020.1.1.9999999" which is not a
valid Node.js package version, and would result in errors when invoking the
npm command. Note that this does not stop pm2 from running the service, but
it would prevent an admin from running npm commands on the service.
Instead of a dot, the build process now uses a dash as the separator, since
that is okay for Node.js package versions (e.g. "2020.1.1-999999" is okay).1 parent 493155a commit 1bac49c
File tree
4 files changed
+4
-4
lines changed- build
- rpm
- ubuntu16
- ubuntu18
- ubuntu20
4 files changed
+4
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
55 | 55 | | |
56 | 56 | | |
57 | 57 | | |
58 | | - | |
| 58 | + | |
59 | 59 | | |
60 | 60 | | |
61 | 61 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
44 | 44 | | |
45 | 45 | | |
46 | 46 | | |
47 | | - | |
| 47 | + | |
48 | 48 | | |
49 | 49 | | |
50 | 50 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
44 | 44 | | |
45 | 45 | | |
46 | 46 | | |
47 | | - | |
| 47 | + | |
48 | 48 | | |
49 | 49 | | |
50 | 50 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
44 | 44 | | |
45 | 45 | | |
46 | 46 | | |
47 | | - | |
| 47 | + | |
48 | 48 | | |
49 | 49 | | |
50 | 50 | | |
| |||
0 commit comments