From bb4060bcb6e194cdf30a20d0761e3e43025e5c29 Mon Sep 17 00:00:00 2001 From: Robert Date: Wed, 3 May 2023 10:38:06 +0100 Subject: [PATCH] Add note about how to find VSCode node version --- docs/releasing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/releasing.md b/docs/releasing.md index 6aefdcf0b..86706f720 100644 --- a/docs/releasing.md +++ b/docs/releasing.md @@ -10,7 +10,7 @@ * New telemetry events are added. * Deprecation or removal of commands. * Accumulation of many changes, none of which are individually big enough to warrant a minor bump, but which together are. This does not include changes which are purely internal to the extension, such as refactoring, or which are only available behind a feature flag. -1. Double-check that the node version we're using matches the one used for VS Code. If it doesn't, you will then need to update the node version in the following files: +1. Double-check that the node version we're using matches the one used for VS Code. You can find this info by seleting "About Visual Studio Code" from the top menu. If it doesn't match, you will then need to update the node version in the following files: * `.nvmrc` - this will enable `nvm` to automatically switch to the correct node version when you're in the project folder * `.github/workflows/main.yml` - all the "node-version: '[VERSION]'" settings * `.github/workflows/release.yml` - the "node-version: '[VERSION]'" setting