From ed8405d555773bb51ed3f80057b62877e3809635 Mon Sep 17 00:00:00 2001 From: Heliozoa Date: Fri, 26 Jan 2024 13:14:19 +0200 Subject: [PATCH] Add instructions for testing the packaging --- CONTRIBUTING.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8aa17f9b..aea5ec7e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -106,6 +106,8 @@ You can update the `package-lock.json` version with `npm i --package-lock-only`. You can run the script manually by giving the GitHub release tag you're going to use as an argument. For example `./bin/validateRelease.sh v3.0.0-prerelease`. +The extension is packaged using the script `./bin/package.bash`. Like the validation script, you should install and test the resulting package manually to ensure there's no problems with the packaging. (You can install the extension from the package by selecting `Extensions: Install from VSIX` from the command palette) (TODO: automatically test the actual package somehow?) + ## Other notes Running the extension produces the following superfluous warnings: