wrapper/tailwindcss
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

Force creating an npm version for insiders build (#5423)

Browse source 
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.
This commit is contained in:
Robin Malfait 2021-09-07 14:30:55 +02:00 • committed by GitHub
parent d01091d44d
commit 2b9c4fec1f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.github/workflows/release-insiders.yml vendored
View file

@ -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