mrva/vscode-codeql
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Update VS Code version documentation

Browse Source
This commit is contained in:
Koen Vlaswinkel
2024-01-03 11:44:19 +01:00
parent 9718aa5806
commit 4b49a8f9bb
1 changed files with 3 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/vscode-version.md
View File

@@ -27,16 +27,11 @@ Also consider what percentage of our users are using each VS Code version. This
To provide a good experience to users, it is recommented to update the `MIN_VERSION` in `extension.ts` first and release, and then update the `vscode` version in `package.json` and release again. To provide a good experience to users, it is recommented to update the `MIN_VERSION` in `extension.ts` first and release, and then update the `vscode` version in `package.json` and release again.
By staggering this update across two releases it gives users on older VS Code versions a chance to upgrade before it silently refuses to upgrade them. By staggering this update across two releases it gives users on older VS Code versions a chance to upgrade before it silently refuses to upgrade them.
When updating the minimum version in `package.json`, you should also follow the additional steps listed below. After updating the minimum version in `package.json`, make sure to also run the following command to update any generated
files dependent on this version:
### Updating the Chromium target version
For the webview code, we use [esbuild](https://esbuild.github.io/) to bundle the code. This requires a target version of Chromium to be specified.
This version should be the same as the version of Chromium that is bundled with the new minimum VS Code version. To update
the version, run:
```bash ```bash
npx ts-node scripts/generate-chromium-version.ts npm run generate
``` ```
#### Troubleshooting #### Troubleshooting