This fails because we usually use node 14 or 16, which has a package-lock.json version of `2`. However on node 12, this version is `1`. This means that after an npm install the package-lock.json is touched and thus `npm version` fails because git is in a dirty directory. Adding a `--force` is not ideal, but also not really an issue since the only thing that could change is the package-lock.json and this is not published to npm anyways. |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| PULL_REQUEST_TEMPLATE.md | ||