From 9304572da16d0adae42b28a4c4f9a3825a65bc7c Mon Sep 17 00:00:00 2001 From: William Killerud Date: Sat, 2 Mar 2024 20:18:35 +0100 Subject: [PATCH] chore: run install as part of vscode:prepublish I believe the reason the patch release failed last time was that vsce validates that package.json matches node_modules (good thing to have!) so you ship what you think you ship. When the version of the language server package is bumped by semantic-release it only updates the package.json, since it's designed for publishing packages, not publishing built and bundled assets necessarily. At least that's my theory. We'll see next time I guess. No harm in manually bumping the version should it be something else. --- vscode-extension/package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vscode-extension/package.json b/vscode-extension/package.json index 31fae58f..c274d7ec 100644 --- a/vscode-extension/package.json +++ b/vscode-extension/package.json @@ -118,7 +118,7 @@ "shx": "0.3.4" }, "scripts": { - "vscode:prepublish": "npm run build", + "vscode:prepublish": "npm install && npm run build", "clean": "shx rm -rf dist", "build": "npm run clean && webpack --mode production", "dev": "npm run clean && webpack --mode development",