From 2b9c4fec1f129f400548e36ad016c0ba6bec1d89 Mon Sep 17 00:00:00 2001 From: Robin Malfait Date: Tue, 7 Sep 2021 14:30:55 +0200 Subject: [PATCH] Force creating an npm version for insiders build (#5423) 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. --- .github/workflows/release-insiders.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release-insiders.yml b/.github/workflows/release-insiders.yml index e05365c44..eda73df5a 100644 --- a/.github/workflows/release-insiders.yml +++ b/.github/workflows/release-insiders.yml @@ -48,7 +48,7 @@ jobs: run: echo "::set-output name=sha_short::$(git rev-parse --short HEAD)" - name: "Version based on commit: 0.0.0-insiders.${{ steps.vars.outputs.sha_short }}" - run: npm version 0.0.0-insiders.${{ steps.vars.outputs.sha_short }} + run: npm version 0.0.0-insiders.${{ steps.vars.outputs.sha_short }} --force - name: Publish run: npm publish --tag insiders